VS2015 Projucer-generated projects not upgradeable to build in VS2017 with new toolset (v141)

I guess this wouldn’t be a very high priority, but it seems that VS2015 projects generated by Projucer don’t upgrade correctly to build VS2017, in case you choose to oblige VS2017 when it asks you if you want to upgrade your projects to build with new toolset (v141) the first time you open your solution.

This is really easy to reproduce - for example, just try to build the Projucer itself after agreeing to upgrade to the new toolset and it won’t work (I guess the solution to build Projucer was also generated by the Projucer) :slight_smile:

Looking deeper it seems that some references to the old toolset (v140) remain in the Projucer-generated .vcproj files. I guess there’s some incompatibility between what the Projucer generates and what VS2017 expects to see in VS2015 .vcproj files.

The current workaround is just to choose not to upgrade the toolset; note that to be able do that you need either VS2015 installed or to install the older VS2015 toolset component when installing VS2017.

1 Like

Yes, I’m afraid this is what you need to do. But if you are using VS 2017, you should just be using the VS2017 exporter.

That’s what I did.
But, there is no VS2017 build in the develop branch for the Projucer itself
yet, so to build the Projucer itself and start creating VS2017 projects,
you still need either VS2015 or the VS2015 toolset installed :slight_smile:


Please where to find the Juce version with the VS2017 exporter?
The last one on githup has no VS2017 exporter.

You need to checkout the develop branch to get that.

1 Like