Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Downgrading solution from Visual Studio 2017 RC to Visual Studio 2015

I have had a project in VS 2015 Update 3 with a lot of code logic behind. I upgraded it to VS 2017 RC successfully. The code implementation went on and on until getting to the point where VS 2017 RC exhibited a lot of issues and instabilities e.g. .Net Core DLL template removed! by installer or Resource file could not be compiled and so forth! I'd like to revert the solution back to VS 2015 to keep working flawlessly but it's impossible easily due to a lot of code implemented in VS 2017 excluding new Roslyn features. Any suggestions how to perform the downgrade?

like image 216
Arash Avatar asked Dec 08 '16 14:12

Arash


People also ask

Can I open Visual Studio 2017 project in 2019?

Visual Studio 2019 can open projects created in Visual Studio 2013, Visual Studio 2015, and Visual Studio 2017.

How do I change the project type in Visual Studio?

The only thing that can really be changed in terms of the project type is essentially the output type. This can have value Class Library, Console Application and Windows Application. You can change this by going to the project property page (right click Properties) and change the Output Type combo box.

How do I update Visual Studio solutions?

To upgrade a project created in an earlier version of Visual Studio, just open the project in the latest version of Visual Studio. Visual Studio offers to upgrade the project to the current schema. If you choose No, the project doesn't get upgraded.


1 Answers

You will also need to update your *.vcxproj files, to change the toolset referenced there to the one used by the earlier compiler. What I found useful, is to create a small scratch project (just simple console app) in each version of visual studio, then use beyond compare or similar to contrast the .sln and .vcxproj files from each vs version. This will show you the toolset changes and maybe a few others that you need. For example going from vs 2017 to vs 2019 the toolset changes from 141 to 142. So the lines <PlatformToolset>v141</PlatformToolset> are for vs2017 and

<PlatformToolset>v142</PlatformToolset> is for vs2019

like image 80
Paulus Avatar answered Oct 04 '22 08:10

Paulus