0

I have a solution file with a bunch of C# projects. For some of the projects, VS2017 urges me to upgrade the project to a later version. We are in a transition phase where one solution needs VS2017 while the rest of our code base is still using VS2015, hence we don't want to upgrade yet.

I do not understand why some projects are triggering this prompt and some not. They have the same ToolsVersion, ProjectTypeGuids, TargetFrameworkVersion etc.

I am looking for a way to modify the projects so that VS2017 shuts up until we are ready to make the full move to VS2017.

Krumelur
  • 31,081
  • 7
  • 77
  • 119
  • VS 2017 shouldnt upgrade the project files, unless you have .NET Core Projects. Have a look at: https://stackoverflow.com/questions/41944571/is-visual-studio-2017-backwards-compatible-with-visual-studio-2015-solutions – Rand Random Jun 30 '17 at 09:10
  • It shouldn't, and I can just cancel the prompt and everything works. But the prompt makes it easy for developers to accidentally upgrade the project, breaking VS2015 support. (The upgrade changes ToolsVersion to 15) – Krumelur Jun 30 '17 at 09:11
  • What is the project type which VS2017 wants to upgrade? Since you have code base is still using VS2015 and don not want to upgrade to VS2017, Why do not you continue to develop your project on VS2015? Then upgrade it when you ready. – Leo Liu Jul 03 '17 at 02:15
  • .NET framework class lib. Other projects in one solution requires 2017, and the solutions share projects. – Krumelur Jul 03 '17 at 04:20
  • Have a look at https://stackoverflow.com/a/44060441 it is an answer to the same question. – ajcaruana Jul 10 '18 at 13:41
  • No, that is a different issue. In the end I solved this by migrating to the new style C# projects, which brings along a lot of other benefits. – Krumelur Jul 29 '18 at 14:19

0 Answers0