Visual Studio Adding Controls to Full-Featured

I am trying to modify the Full-Featured GUI - the C++ Using MFC version- in Visual Studio 2010 but nothing I do to the resource file seems to "take".
I went through and added a TestStand ActiveX Listbox along with a standard button and listbox. While I can see my changes when I test the dialog box (see attached), when I actually run the application (either in VS 2010 or outside of it) it's like I didn't make a change at all (see attached).
Any ideas as to what's going on here?
Attachments:
UI_Running.gif ‏183 KB
UI_Test_Dialog.gif ‏65 KB

Nevermind. I got it.
I'm used to just placing the controls and running in in older versions of Visual Studio. VS 2010 is new to me so I figured I was doing something wrong. It took me a while to figure out that these GUI samples size/move the controls programatically.

Similar Messages

Visual Studio 2013 is creating new feature every time new list definition is added

We are using Visual Studio 2013 and details are as under:
Microsoft Visual Studio Ultimate 2013
Version 12.0.30501.00 Update 2
We we add a new list definition in our project, it creates a new feature with it. If we delete the feature and add list definition in the existing feature, list is created but columns are not added in the list.
Same thing happened if we rename "Feature1", a new feature is created every time a new list definition is created.
This doesn't happen when we add a Visual WebPart.
Also, we have three different custom list option in the drop down in new list creating wizard.
Is this a bug or we are doing something different.
http://farhanfaiz.wordpress.com

Intellisense has a bug in VS2013 where it doesn't recognize InitializeComponent when you start working on the XAML. My feeling is that if you try to compile this app, it will run fine (as long as there are no actual errors).
Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.
NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined
objects and unknown namespaces.

Limited features for crystal reports in visual studio 2005

Post Author: jag
CA Forum: .NET
Hello All,
I have problems in finding solution for the following problems in line graph in crystal reports in visual studio 2005.
1)Cant customize the colour of line in the line graph. (line by series only i wanted not by group)
2)Cant customize the width of line.
3)Cant customize the line style display.
4)Cant customize the trend line or target line.
Can you please help in resolving these problems....
Do i get any extended crystal report software for visual studio 2005 to get all features in crystal reports 10 r 11 versions?
Do you recommend 3dgraphics macros is better and economical to get extended features of crystal reports in visual studio 2005?
Can anyone please help me..iam in need of these solutions urgently....
Thanks in advance for your time......cheers

Post Author: Argan
CA Forum: .NET
I am not really familiar with all of the options for charting and what is or isnt in the bundled version.
You can download the CR XI R2 developer edition eval from the website and see if it gives you the graph options that you want. If it does then I think you can buy it at an upgrade price since you already have the bundled edition.

C:\Program Files (86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe Side by Side Error

I used the sxstrace tool to find the error but ill admit im not sure what im doing. If you can please help me identify whats wrong that would be great!
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = Wow32
CultureFallBacks = en-US;en
ManifestPath = C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe
AssemblyDirectory = C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\
Application Config File = C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe.Config
INFO: Parsing Application Config File C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe.Config.
INFO: Parsing Manifest File C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe.
INFO: Manifest Definition Identity is WDExpress,processorArchitecture="X86",type="win32",version="1.0.0.0".
INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Reference: debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0"
INFO: Reference: Microsoft.VisualStudio.CompilerHostObjectsProxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0__6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Auto Servicing Policy redirected assembly version.
INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.17514".
INFO: Begin assembly probing.
INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.17514".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll\debuggerproxy.dll.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll\debuggerproxy.dll.MANIFEST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0".
ERROR: Activation Context generation failed.
End Activation Context Generation.

Hello,
I saw a related thread from here:
http://stackoverflow.com/questions/15130609/visual-studio-2012-side-by-side-configuration-is-incorrect
The dll in that thread is different from there but I think you can still try the solution listed there to repair your VS installation.
May I clarify some questions? Can you use Visual Studio before you get this error? Is it the first time you installed Visual Studio and when you try to open it it reports this error for you?
If you can use Visual Studio before you get this error, please try repair Visual Studio from control panel.
If you cannot use Visual Studio even when it is the first time to load, then it is a corrput installtion problem. Please remove the current installation:
http://support.microsoft.com/en-us/kb/2771441 Then download and verify the ISO:https://www.visualstudio.com/en-us/downloads/visual-studio-2013-iso-sha1-vs
And restart the installtion with a healthy ISO.
Anyway, in my mind refer to the first stackoverflow thread and repair the installtion to fix this missing dll problem is more reasonable.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error on Form Designer on Visual Studio 2012

Dear Sir,
I have used Visual Studio 2012 to develop my project for a long time.
However, suddenly Designer of all Forms come an error but the system can compile the project.
Therefore, I am not able to change the design of the Form in Visual Studio.
Any Suggestion?
Thank you very much.
The following is the Error of the Designer:
To prevent possible data loss before loading the designer, the following errors must be resolved:
1 Error
The type 'System.Configuration.UserScopedSettingAttribute' could not be found. Ensure that the assembly containing the type is referenced. If the assembly is part of the current development project, ensure that the project has been built.
Instances of this error (1)
1. Hide Call Stack
at Microsoft.VisualStudio.Design.VSTypeResolutionService.System.ComponentModel.Design.ITypeResolutionService.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
at Microsoft.VisualStudio.Design.VSTypeResolutionService.System.ComponentModel.Design.ITypeResolutionService.GetType(String name, Boolean throwOnError)
at Microsoft.VisualStudio.Shell.Design.VirtualTypeBuilder.FillAttributes(Resolver resolver, CodeTypeMember member, Attribute[]& customAttributes, MemberAttributes& memberAttributes)
at Microsoft.VisualStudio.Shell.Design.VirtualTypeBuilder.InitializeFromType(ITypeResolutionService typeResolutionService, CodeTypeDeclaration typeDecl, String namespaceName)
at Microsoft.VisualStudio.Shell.Design.VirtualTypeBuilder.InitializeFromType(ITypeResolutionService typeResolutionService, CodeNamespace ns)
at Microsoft.VisualStudio.Editors.SettingsGlobalObjects.SettingsFileGlobalObject.BuildType()
at Microsoft.VisualStudio.Editors.SettingsGlobalObjects.SettingsFileGlobalObject.GetObjectType()
at Microsoft.VisualStudio.Shell.Design.GlobalType.get_ObjectType()
at Microsoft.VisualStudio.Shell.Design.GlobalObject.GetHashCode()
at System.Collections.Generic.ObjectEqualityComparer`1.GetHashCode(T obj)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Microsoft.VisualStudio.Shell.Design.GlobalObjectService.TrackGlobal(GlobalObjectProvider p, GlobalType g)
at Microsoft.VisualStudio.Shell.Design.GlobalObjectService.GetGlobalObjects(Type baseType)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetTypeFromGlobalObjects(String name, Boolean throwOnError, Boolean ignoreCase)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String name)
at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetType(String typeName)
at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.EnsureDocument(IDesignerSerializationManager manager)
at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)
Best regards,
Felix

Hello Felix,
The info seems tell us your project is corrupt. May I ask this question, will this error reproduce when you create a new simple project? This can be divided into two scenarios:
Scenario 1: The new project is also corrupt.
In that way, your Visual Studio may already corrupt. It's time for you to repair your Visual Studio from control panel.
If it still not work, try use some common steps below to fix:
Please open an administrative CMD window and navigate to C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE and run these commands:
1.devenv.exe /safemode
2.devenv.exe /resetskippkgs
3.devenv.exe /installvstemplates
4.devenv.exe /resetsettings
5.devenv.exe /resetuserdata
Scenario 2: The new project doesnot get this issue.
In this way, we should focus on this "The type
'System.Configuration.UserScopedSettingAttribute' could
not be found"
See here from MSDN to know how we can use it in our code:
https://msdn.microsoft.com/en-us/library/system.configuration.userscopedsettingattribute(v=vs.110).aspx
Check whether your code list something like below code and check whether you have missed anything here.
//Application settings wrapper class
sealed class FormSettings : ApplicationSettingsBase
[UserScopedSettingAttribute()]
public String FormText
get { return (String)this["FormText"]; }
set { this["FormText"] = value; }
[UserScopedSettingAttribute()]
[DefaultSettingValueAttribute("0, 0")]
public Point FormLocation
get { return (Point)(this["FormLocation"]); }
set { this["FormLocation"] = value; }
[UserScopedSettingAttribute()]
[DefaultSettingValueAttribute("225, 200")]
public Size FormSize
get { return (Size)this["FormSize"]; }
set { this["FormSize"] = value; }
[UserScopedSettingAttribute()]
[DefaultSettingValueAttribute("LightGray")]
public Color FormBackColor
get { return (Color)this["FormBackColor"]; }
set { this["FormBackColor"] = value; }
Or you can copy your project content to a new fresh project and rebuild your project with new settings.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Visual Studio 2013 slows down + crashes when using Source Control features.

I have spent two full days trying to resolve this issue but no luck so here we go,
I have created a project using Visual Studio Team Foundation Server plug-in in the past. Later on I switched to
Microsoft Git Provider.
Now when I connect to that project in the Team Explorer and double click on the solution to work on it locally it somehow changes the plug in to Microsoft Git Provider automatically and of course I can't
Commit/Commit and Push since I receive following error in the Team Explorer,
An error occurred. Detailed message: Failed to open directory 'C:/Users/.../AppData/Local/Application Data/'
Manually changing the plug-in to the Visual Studio Team Foundation Server
results in a broken Team Explorer as below,
With Settings leading to an empty pane, and also a warning in the Team Explorer's Changes page telling me the message below if I click on Pending Changes...
Microsoft Git Provider is not the current Source Control plug-in. Change Plug-in
And manually selecting the solution from Solution Explorer, right click and
Add Solution to Source Control, leads to never ending hour glass and (Not responding) visual studio.
New Projects
Creating a new project is straight forward, unless I "Add to Source Control" is checked. If so, again never ending process if Microsoft TFS plug-in is selected in the tools and eventually me Ending the Visual Studio task. And a VERY long process
(40+ mins) if I have chosen Microsoft Git but that finishes successfully rather.
New TFS project from Team Explorer
If I create a new project in my Online Web Studio
Click on Open with Visual Studio Link => Opens and connects to a my newly created TFS in team explorer.
Clicking new in Team Explorer under Solutions to create a new solution and bind it to this Repo
leads to straight crash of Visual Studio and restarting attempt of VS.
So I really can't use Source Control from visual studio other than cloning GitHub's existing repo's on Visual Studio and Committing my current Microsoft Git managed projects.
I have attempted
Repairing Visual Studio (no luck in results)
Devenv.exe /setup (no luck)
Trying to scrap the SCC info on my solution then at least it won't get picked up by source control then I can Check it in as a new project. (no luck and the solution picks the Microsoft Git upon opening it by clicking on the .sln file.) I have followed
these steps in this stack overflow answer.
And lots of mucking around like removing my workspaces almost Thousand times and putting them back, binding and etc.
I am really stuck on this and it's holding me back from staring a new project (which is problematic using Adding to Source Control) and unfortunately is dependent on the old project (which is developed under Visual Studio Team Foundation Server Plug-in which
is throwing tantrums)
Would like to hear you pro-s input on this
Using
Visual Studio 2013 Community edition (recently switched from Pro to Express to Community)
Windows 7 (64-bit)
Git tools
Git windows installation
Nuget Package manager
Visual Studio Log File
http://filesave.me/file/50620/log-txt.html
Mehradzie

Hi Mehradzie,
Based on the description, seems you're working with Git team project in Visual Studio Online(formerly Team Foundation Service). I'd like to know whether you mean Visual Studio Git command tool as the plug-in, and if you're trying to create solutions/projects
with Visual Studio and add them to the created Git team project.
From the screenshot, you're not connect to the Git team project by using Team Explorer. To work with Git team project locally, you can follow the instructions as below:
Connect to Git team project by using Team Explorer, after that you might install Git tools if you connect to the team project for the first time
Clone the remote Git repository to a local git repository and set the path to local git repository
Create a solution and select Git source control, also saved to the local path of the local git repository
Select your branch, and then click "Changes" and Commit the changes
Click "unsynced commits" and push the commit to remote git repository
You can also refer to the links below for more information about getting started with Git in Visual Studio Online.
http://www.visualstudio.com/en-us/get-started/share-your-code-in-git-vs.aspx
http://blogs.msdn.com/b/visualstudioalm/archive/2013/01/30/getting-started-with-git-in-visual-studio-and-team-foundation-service.aspx
If you still have any other concerns, please elaborate more details about your scenario. Thanks for your understanding.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Visual Studio keeps adding SharePoint features when opening a solution

Hello everybody.
I'm facing a rather naughty problem. In a Windows 2012 environment (hosted inside an Azure virtual machine), with SharePoint installed, I created a VS SharePoint on-premise solution. I added a feature, and started adding lists, libraries, site columns, layout
pages and such. At one point, every time I added a new list definition, the VS would create me a new feature. Which is not what I wanted, so I manually deleted the new feature and added the list to the first feature. No matter how much I try, VS keeps adding
features instead of using the one I already got.
But that's a minor problem. After a while of adding lists, I did a check in to my TFS and closed the VS. After a couple of days, I open the VS again, and without a warning VS checked out the solution, checked out my only feature, removed the lists from it
and created one feature for each library. I ended up with feature2.feature, feature3.feature, ..., feature50.feature files!!! Insane!!! I had to manually delete them and re-add them to my first feature.
Now I can't turn VS off without having this mess all over again. Why on Earth would somebody program VS to do this? Is there any way to turn this behaviour off?
Thanks in advance!
[Edit] Forgot to mention that I'm working with Visual Studio 2013.
Fernando A. Gómez F.
fermasmas.wordpress.com
Galería de ejemplos

Hi Fernando,
Thank you for posting in MSND forum.
Based on your issue, could you please tell me what template sharepoint project you create in VS2013?
In addition, I find a similar thread about your issue, please refer the Xiaoying’s reply to check this issue.
http://stackoverflow.com/questions/25857722/visual-studio-unexpectedly-adding-feature-on-load
Or you could try to download a new sharepoint template in this VS2013 and then create it check if you still get the issue.
I suggest you could try to create a same sharepoint project template from VS2013 on another machine and then check this issue again.
If you have any update message, please feel free to let me know.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Problems adding a custom SSRS (PolygonsCRI demo project) control to Visual Studio 2012 toolbox

I've been trying to create a custom control in SSRS using the PolygonsCRI example. I've finally got the solution to compile in Dot Net 4.5 under Visual Studio 2012 targeting x86 architecture. (x86 seems to be the only way to compile without complaints
about architecture mismatch involving some of the key reporting DLLs.) I'm running VS2012 Premium, version 11.0.61030.00 Update 4.
I still can't use it in the Polygons demo reporting project.
I can add the DLL to the toolbox but all I get is a red rectangle and the message 'The custom report item type PolygonsDesigner is not installed'.
Suggestions? I'm out of ideas at this point.

Hello,
You have "add DLL to Toolbox"?
See Jazz Up Your Data Using Custom Report Items In SQL Server Reporting Services => Deploying CRI: You have to Register you CRI in "RSReportDesigner.config" file.
See also MSDN:
How to: Deploy a Custom Report Item
Olaf Helper
[ Blog] [ Xing] [ MVP]

Missing controls when in resource manager of visual studio 2005

I'm trying to port an application to Visual Studio 2005. It uses GPIB and Serial controls. When I double-click on the
dialog to bring it up to look at the controls, an error is displayed saying that the controls could not be instantiated, reinstall or register the
controls and try again. I have installed and have Measurement Studio in my Visual Studio 2005. I know this is probably vague,
but ANY help would be greatly appreciated!

Hi KBr,
I assume you were using the CWGPIB and CWSerial ActiveX controls right? What
version of Visual Studio were you previously using (VS 6.0, .NET 2003)? Also
what language were you programming in (C++, VB, etc) and what language are you
in now (C++, VB.NET, C#)?
Also what version of Measurement Studio did you purchase (Standard,
Professional or Enterprise)? The reason I ask is that those CWGPIB and CWSerial
ActiveX controls are legacy components and you will need the Measurement Studio
for Visual Studio 6.0 support to have these components. This CD only comes with
the Professional and Enterprise versions of Measurement Studio.
My guess is that you only have the Standard Edition which doesn't come with the
VS 6 support.
If you are programming in .NET (C#, VB.NET), I highly
recommend that you use the native .NET VISA and GPIB class libraries with
Visual Basic .NET rather than the ActiveX controls. The .NET class libraries
are more full featured, exhibit better performance, and should be much more
natural to use in VB.NET or C# than the ActiveX controls.
Hope this helps!
Best Regards,
Jonathan N.
National Instruments

Adding a ECB item menu action to a declarative Visual Studio 2013 Workflow

Hi
I have build a Sandbox 2013 workflow in Visual Studio which I can attach to my desired list. I want my users to be able to trigger this workflow via the item ECB menu as your can in an App Client Control. Is this easy to do say with a feature
- assuming you specify the list on workflow initiation.
Do I need to import my workflow into SPD 2013 and play around with Actions but that sounds a bit dodgy!
Regards
Daniel
Freelance consultant

Hi Daniel,
According to your post, my understanding is that you want to add ECB menu and start a
special workflow.
The following materials would be helpful:
Start a workflow with SharePoint (JavaScript)
https://gist.github.com/Aymkdn/3873181
Using ECMAScript Client Object Model from ECB Custom Actions
http://pholpar.wordpress.com/2011/04/08/using-ecmascript-client-object-model-from-ecb-custom-actions/
If I misunderstand what you mean, please provide more information about your requirement for further research.
Thanks,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Dennis Guo
TechNet Community Support

Is there any way to control the zoom factor so that when my SSIS Package is opened, it is entirely visible within Visual Studio?

I have formatted my SSIS Package beautifully, if I do say so myself, so that all my tasks are visible at 50% zoom. However, when I close my project and then re-open it in Visual Studio, it defaults back to 100%...YUK!
I did find this post which didn't seem to work...even to the point that no where within my xml could I even find the "PersistedZoom" Parameter. I even tried manually adding it, I couldn't find the exact syntax on it, and that didn't even work.
1. In BIDS (Visual Studio) first close all open SSIS packages / xml files to avoid confusion ...
2. Right click on the SSIS package and select the "View Code" menu item. (to open the actual xml)
3. Search for all instances of "PersistedZoom" and change the value directly to the right of it to 100 (mine
was 80 or 90 ...)
4. Now save and close the XML file.
5. Now open the SSIS package in the designer, you will notice that it is still scrolled to the bottom right!
6. Now make any small change (I scrolled to the top-left and just slightly moved a task)
7. Now save and close the designer
8. Re-open the SSIS package in the designer! and what do you know it does not start scrolled down to the bottom right anymore!
Let me know if you still have issues - but as I said I followed this same process on all my problem packages and they ALL now open correctly.
I noticed that after doing all this the PersistedZoom property disappeared from the xml, which leads me to believe that if I zoom in and out of my packages again it will probably get stuck by opening to the bottom right again ...
Can anyone help me out with this?
Thanks for your review and am hopeful for a reply.
PSULionRP

There is no way to preserve view preferences.Just remember or annotate the zoom % used in the package.
You may want to open an MS Connect item asking to add such a feature.
I can tell you it may not be implemented because a package may be opened on different size monitors.
Arthur My Blog

Visual Studio 2013 Pro - Winforms toolbox icons beside items are missing for some 3rd party vendors controls

I noticed last weekend after installing VS 2013.4 update that the Winforms toolbox, while showing all items, did not display the icons beside the items for any custom/third party Winform controls. The only icon
showing in the toolboxes are the Pointer icon. I can select and drop any control onto a project, and as soon as I move mouse into the design surface the icon shows. Neither the
builtin Winforms controls nor the WPF toolbox exhibit the same symptom. It is specific to Winforms third party controls (ActiPro and DevExpress). At first I thought it was due to the update, then I found that my laptop was
already exhibiting this symptom, running 2013.3 (I had not dropped any controls from the toolbox in the past few weeks so I did not notice).
The two machines (laptop and workstation) are running Windows 7 64-bit Professional and Ultimate, respectively. These machines are dedicated to development, and are secured, also running Norton Antivirus.
I also have VS 2010 and VS 2012 which don't exhibit the symptom, though I finally removed 2012 last night during my adventures. I had all three VS side by side, running well for months (I added VS 2013 in June). VS
2013 had been functioning well on a daily basis for the dozen or so Winforms projects and the odd WPF or MVC project.
I use DevExpress v2014 and ActiPro controls; I have been using them for years now.
I've spent 2 days trying remedies that include:
Resetting Toolbox
Removal of *.spd files in %APPDATA%, restarting VS
Uninstall Visual Studio, remove and delete of any Visual Studio remnant in the registry, Program Files(x86), %APPDATA% and %PROGRAMDATA%, reinstall.
Repeat step 3 with VS 2013.1 and .3
Downgraded .NET to 4.5.1 to match my third, correctly functioning computer (also running Windows 7 x64 Ultimate).
DevExpress has told me this isn't a problem they have seen. At first I agreed, since my ActiPro controls also are missing their icons, but then I noted that other vendor controls display fine. Not sure what else to do but to nuke the workstation and install
from OS up.

DevExpress is discussing this issue in the thread here : https://www.devexpress.com/support/center/Question/Details/T174133#comment-a98eedf1-ca54-4920-a2d6-49506ddae5b5
The small sample they provided in the thread actually reproduces the bug in my environment.
Since I cannot post screenshots here on MSDN forum (I explained above, when I try to attach pictures I
receive an error that my account is not verified). There is nothing more I can do.
This appears to be a bug in Visual Studio 2013. VS 2010 and 2012 are on the same machine and do not exhibit
the problem. It is frustrating how unresponsive Microsoft is to my issue. I am a long-time MSDN subscriber, as well as customer of multiple seats of the retail copies of Visual Studio. It looks like the only way to get attention is to pay for a incident. If
Microsoft is interested in actually seeing this bug in action, I have 2 machines that are preserved. I have installed a fresh environment on my backup PC.

How to change feature id in an existing Visual Studio solution

I have created a Visual Studio solution containing all the required design elements (like master pages and user controls) that I would be re-using in all my new applications. I created a visual studio template using (File -> Export Template) and I am
able to create new solution based on it.
I have changed the assembly name, solution id with new Guid. The problem is with Feature Id. I noticed that even when I changed the feature id and id (in feature.xml) with new Guid it still overwrites the existing feature already deployed on the farm instead
of creating a new feature.
Please advise whether it's possible to re-use a visual studio template with existing features.

Hi,
Try to create the new blank SharePoint project and include these features or create new feature and update the feature.xml file with old feature.xml content except the scope and feature Id in the new feature file.
So you'll get new assembly to be deployed on GAC.
You cannot change the the SharePoint's default feature id and their's scope.
May be the assembly binding or redirection is not working as expected in the old assembly name.
Murugesa Pandian| MCPD | MCTS |SharePoint 2010

Visual Studio error when trying to open a Feature in a SharePoint Project (An exception occurred while calling 'OnImportsSatisfied')

I am getting the following error message in both Visual Studio 2012 and Visual Studio 2013 when I try to open any "Feature" in a SharePoint 2013 project.
An exception occurred while calling the 'OnImportsSatisfied' method on type 'Microsoft.VisualStudio.SharePoint.Designers.Package.ViewModels.FeatureViewModel'.
(the stack trace then continues on for ages - shown in full below)
I _think_ this started happening when I ran Windows Update recently.
This happens for both old and new projects, both Sandbox and Farm solutions.
I have tried:
Removing all Windows Updates from the past week
Removing all previous versions of Visual Studio (2012)
Completely uninstalling and reinstalling Visual Studio (with reboots inbetween)
Installing VS2013 Update 1
Nothing that I do seems to fix this ..
Full Error:
regards
Martin Hatch
MCPD & MCITP SharePoint 2010
MCTS WSS 3.0 | MOSS 2007
www.martinhatch.com

Hi,
Please check that whether you have installed the Microsoft Office Developer Tools for Visual Studio 2012.
The link below will provide more details:
Prerequisites for creating SharePoint 2013 projects using Visual Studio 2012
Best regards
Patrick Liang
TechNet Community Support

Adding Columns to the matrix in SAP B1 user form using Visual studio 2010

Hi,
Using Visual studio 2010, I have created a SAP B1 user form( b1f ) with one matrix.Matrix is having 5 columns. Its working properly. Later, I want to add few more columns. Then I added columns to the matrix as I have created columns initially. But, it does not saves.
i.e, Whenever I run, In B1 I could see only old columns. Newly created columns are not showing.So, I closed the .net project and opened again. Created columns are not showing in visual studio b1f itself. So, I created again and saved. But, its not saving.I tried it many times.
What I am missing?
Any help is appreciated.
Thanks in advance,
Parvatha Solai.N

Hi Parvatha,
Are you using B1 Studio? Anyway try to clean the solution first then rebuild it. This would re-copy files to the output directory, that contain your changes.
Best regards,
Pedro Magueija

Visual Studio Adding Controls to Full-Featured

Similar Messages

Maybe you are looking for