Here’s the official history, from Cameron McColl: In Dev10 we invested in improving solution load time by looking at making the load asynchronous. Unfortunately due to time constraints this work didn’t make it into Dev10 so instead we decided to at least make the user experience slightly better by giving the user feedback on what … Read more
C++ and C# Look at the sidebar in this link
I’m sorry to tell you that the publish.xml file which VS2010 uses was not designed to be used in this way. In fact it was not even designed to be checked-in/shared with others. The logic for reading/writing those files are strictly contained inside Visual Studio and not available through MSBuild. So there is no straight … Read more
Open the pending changes window. You can find there a toolbar button that filters on the current solution.
Actually, you can add folders to F# projects but it’s not supported directly through Visual Studio (you have to edit the project file yourself): http://fsprojectextender.codeplex.com/ (edit: old link was broken, updated to F# Project Extender home page which has links to the original blog posts which were moved) (which I found in this answer). I … Read more
You can also try using the XDT Transformation Tool: http://ctt.codeplex.com was moved to Github https://github.com/greenfinch/ctt I’m using this instead of messing with obscure msbuild targets.
Check the VC++ directories, in VS 2010 these can be found in your project properties. Check whether $(WindowsSdkDir)\lib is included in the directories list, if not, manually add it. If you’re building for X64 platform, you should select X64 from the “Platform” ComboBox, and make sure that $(WindowsSdkDir)\lib\x64 is included in the directories list.
In the menu select View -> Other Windows -> Document Outline. In that window you see the hierarchical view of your components. Drag the controls to their new parent.
Simply restart Visual Studio, and it will get unstuck. It’s a bug in Visual Studio. Microsoft isn’t going to fix it. Microsoft isn’t going to release the source code so anyone else fix it. Microsoft isn’t going to even investigate the issue. So we are where we are: you have to workaround their bugs.
Open the Properties Window (NOT the right-click on the set-up project) Use the toolbar View -> Properties Window VS 2013/2017 on windows 7: Keyboard shortcut F4 VS 2010 on windows 7: Keyboard shortcut sequence Ctrl + W and then Ctrl + P Now select your set-up project in the Solution Explorer window, the Properties window … Read more