I know of two ways to do it. Method 1 The first method (which I prefer) is to use msbuild: msbuild project.sln /Flags… Method 2 You can also run: vcexpress project.sln /build /Flags… The vcexpress option returns immediately and does not print any output. I suppose that might be what you want for a script. … Read more
As far as I know you can uncheck the “Edit and Continue” checkbox. Tools -> Options -> Debugging -> Edit and Continue > Enable Edit and Continue (uncheck)
There’s a drop down just above the code window: It’s called Navigation bar and contains three drop downs: first drop down contains project, second type and third members (methods). You can use the shortcut Ctrl + F2 (move focus to the project drop down) and press Tab twice (move focus to the third drop down) … Read more
To use unsafe code blocks, the project has to be compiled with the /unsafe switch on. Open the properties for the project, go to the Build tab and check the Allow unsafe code checkbox.
A colleague found this MS auto-uninstall tool which has successfully uninstalled VS2008 for me and saved me hours of work!! Hopefully this might be useful to others. Doesn’t speak highly of MS’s faith in their usual VS maintenance tools that they have to provide this as well!
To generate an area where you can specify a description for the function and each parameter for the function, type the following on the line before your function and hit Enter: C#: /// VB: ”’ See Recommended Tags for Documentation Comments (C# Programming Guide) for more info on the structured content you can include in … Read more
This happens when the following is in the .sln file: GlobalSection(ExtensibilityGlobals) = postSolution MyGlobalProperty = AnyValue EndGlobalSection I found that Enterprise Library added one of these. I removed it, checked in the solution, closed then re-opened it, and no more automatic check out.
What typically helps to fix it is deleting the Solution User Options aka “SUO”. VS up to 2013 In the older VS it is stored as a “hidden” SolutionName.suo in the same folder as the main .sln file. VS2015 or later In VS2015 the same data was moved to a “hidden” .vs folder under the … Read more
Also found in the article mentioned by Tzury, but to sum up the answers in this thread: Make sure Visual Studio is not running when changing the registry key or it will be overwritten on exit with the old value Visual Studio 2022: Follow these instructions, then reboot. Visual Studio 2019: Follow these instructions, then … Read more
If you have a project reference, it should work immediately. If it is a file (dll) reference, you need the debugging symbols (the “pdb” file) to be in the same folder as the dll. Check that your projects are generating debug symbols (project properties => Build => Advanced => Output / Debug Info = full); … Read more