so I messed up some project properties (values in VC++ Directories and so on) and dont know how to go back. Is there any way to get back to default properties (same when I installed visual studio). ReInstallation did not help.
Related
Ever since I installed Visual Studio 2017, it now wants to be the one to open all of my projects. Before installing 2017, if I double clicked a VS 2010 .csproj or .sln in Explorer (Windows 10), it would open in VS 2010. But now opening a project for all previous versions opens in 2017. Even if I right-click and choose Open With > Microsoft Visual Studio Version Selector it always chooses 2017. To open it in the correct version of Visual Studio, I have to first open VS and then browse to the project to open. This is a pain when I don't remember which version the project should open with and just want to click it and open it. Can I reset it to open a project in the version of visual studio it belongs with?
I confirmed how this is meant to work with the team. The only requirement is that you set Microsoft Visual Studio Version Selector as the Default App for .SLN files in Windows. That app launches the version of Visual Studio specified in the solution file. If you crack open a .sln file in an editor, you'll see a section that specifies the version of VS that should be used. It'll look something like this:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 15
VisualStudioVersion = 15.0.25909.2
One thing to keep in mind though is that value will change whenever a different version of Visual Studio writes to the solution file. E.g., if you create a solution in VS 2010, close VS 2010, launch VS 2017, open the same solution, add a project to it (this is what forces VS to make a change to the .sln file), the version in the solution file will then change to VS 2017. I.e., the last version of VS to write to the solution file, will be set as the version to be used when opening it.
If you're finding it's not working as described, we likely have a bug here. Let me know if that's what you think is happening.
I wrote a solution with Visual Studio 2015.
I copied the solution to a PC which has only Visual Studio 2013.
In the Project Properties I have changed the Platform Toolset to Visual Studio 2013 (v120).
The error still remains and I am not able to compile the project. Any suggestions?
Thanks.
If msbuild still complains about v140, this likely means v140 is still in the project file - which you can verify with a text editor.
Are you sure you changed the toolset for all platform/configuration combinations? For instance if you just open the settings dialog and it happens to be showing properties for Debug|Win32 and you change one of those, but then you build Release|Win32, the latter combination will still use v140. Open the proprties dialog again and verify all platforms and configurations use the correct toolset. Or use find/replace from v140 -> v120 in a text editor
I have a open source project that include Visual Studio project files. There is a solution file with four projects files. When the source files are distributed and unpacked, Visual Studio picks the wrong project as the default project. New users don't know they need to right click a certain project, and then select Set as Startup Project.
I've tried re-ordering the projects in the solution file so the appropriate project is first, and I tried changing the UUID on the appropriate project so its the lowest. Neither have helped with the problem of Visual Studio selecting the wrong startup project.
The Visual Studio versions I test against are Visual Studio 2005, 2008, 2010, 2012, 2013 and 2015.
What determines the default startup project?
What can I do to ensure Visual Studio selects the correct startup project?
A related question is Why is “Set as Startup” option stored in the suo file and not the sln file?, but it asks "Why..." and does not ask "How To...".
If there is a *.suo file, the Startup Project is saved there.
Otherwise, the first project listed in the *.sln file will be the Startup.
(tested with VS 2013)
I just joined a new project and the compiled source code of my team member has the Runtime version comment "4.0.30319.1" placed on every *.g.cs. I installed the latest visual studio with service packs and tried to run our project but suddenly my SVN icons have turned red on most files because Visual Studio 2010 automatically changed the Runtime Version comments to "4.0.30319.269" on all the *.g.cs files even though I did not change those files.
Is there a way to stop Visual Studio 2010 from doing this? I would change and commit all the changed files but then my teammate will have several files in red.
I know some may suggest to ask all team mate to install the same service pack and runtime, but I would like to know if this feature can be turned off.
Visual Studio 2010 appears to be referencing the corresponding Visual Studio 2008 folder for all installed item and project templates, even when I do the export template and check the box to install the template I just created, it stores the zips into the 2008 folders and I can confirm that it is looking in there for templates because I was pulling my hair out figuring why the templates I was dropping into the 2010 folder weren't coming.
How can I tell VS 2010 to stop being dumb?
Figured this out:
Tools -> Options -> Projects and Solutions -> General, there you choose the path for item and project templates. Not sure how or why mine was set to 2008.