Retarget the solution to VS2019 Build tools (v142) to allow support for Visual Studio 2019, out-of-the-box.

Problem Statement
Developers cannot use Visual Studio 2019 to build this solution without installing older Visual Studio 2017 Build Tools (v141). These can be hard to find for the everyday dev, requiring you to go to MSDN downloads and search specifically for the required version.

Note: those Build Tools can be quickly found here.

Evidence or User Insights

Steps to Reproduce:

1. Clone this repo with only Visual Studio 2019 installed.
2. Attempt to Rebuild

=> You are not able to build, due to failed checks for the v141 Toolset

Proposal
Retarget the solution, which is literally a two-click process:

1. Open the Solution in Visual Studio 2019 and right click on the solution head
2. Select 'Retarget' and click OK.

The default toolset version will be preselected as v142 by default.

Goals

• Stay in sync with Microsoft's vision of using modern tooling
• VS2019 is significantly faster to use than VS2017 (this is proven, not just anecdotal).

Considerations

This may affect developers who have not updated to Visual Studio 2019 yet if there's no backwards check in the toolcheck list. This can be mitigated by making sure v141 is still in the list after adding v142.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

We should definitely do this; we'll just need to decide when. We'll need to update the official builds to target the 'Hosted VS2019' pool at the same time.

These can be hard to find for the everyday dev, requiring you to go to MSDN downloads and search specifically for the required version.

Easier way, you can install it directly from Visual Studio Installer!

I agree with @mcooley, I would recommend to wait a little (and a couple of VS updates) before really migrating, sorted by importance:

• Not everyone has a MSDN subscription, it can take months before enterprises migrate to VS2019 (a lot of them buy licenses, not subscriptions, VS Community is free but a lot would prefer to use the Pro/Enterprise version if they already use these versions with 2017)
• Visual Studio has always some stability issues with first versions, including 2019 (see dev forums + some mailing-lists 😉)
• IT will need some time to test, whitelist, package and deploy VS2019.
• Not all extensions and plugins are ported for the moment, it can be an issue for accessibility.
• Not all developers have access to a high-speed internet connection (~3GB of data to download), or are traveling, let's them some time to update their systems.
• Developers currently working on a PR should get alerted ~2 weeks in advance, so they can work on their diff without having to manage a VS migration.

IMO we should:

• add a paragraph or a link in README.md explaining how to install 14.1 build tools with VS2019
• Once decided, indicate the migration date minimum 2 weeks before in README.md + a pinned message in the Issues tab
• If possible, create an extra build-agent modifying all .vcxproj files to use v14.2 instead of v14.1 and trying to build the app, so we can track if a PR breaks the compatibility (It should not append, but it can still be interesting to do it). Bonus point: we will already have agents set up when the app will really migrate to v14.2

Is there a solution to this?

I've run into this issue today, and retargeting the solution is not an option. There needs to be a way to install the v141 platform tools for use with Visual studio 2019. The various build tools are not recognized as (Platform Toolset = 'v141').

@provencher You can quickly add the v141 toolset to VS2019. Here are the steps:

1. Open VS Installer
2. Change to the Additional components tab
3. Scroll down until you see the MSVC 141 tools section and select the desired version (I chose the x86/x64 version because I'm only building for x64 locally)

Here's a screenshot to guide you:

@LanceMcCarthy I've installed everything marked as v141 build tools on VS2019, but it does not add the VS2017 Platform toolset to the dropdown in my project's properties folder.

I get this error trying to build:
2>C:Program Files (x86)Microsoft Visual Studio2019ProfessionalMSBuildMicrosoftVCv160Microsoft.CppBuild.targets(378,5): error MSB8020: The build tools for Visual Studio 2017 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install Visual Studio 2017 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting 'Retarget solution'.

I've installed the linked VS2017 build tools and added the v141 tools in the individual section as well

On VS2019 you can see I've added the vs2017 build tools

Something must be missing, here's what I see (on the Caluclator project):

Do you have the UWP SDK installed for that target release (17763)? Is the current configuration set to x86 or x64? Batch print adobe reader.

Yes I do. I primarily dev for UWP.

I finally got everything working, but it required me fully installing vs2017.

Good to see that you're not blocked anymore, but VS2017 shouldn't be required (I don't have VS2017 installed anymore).

Here's my VS2019 configuration export (VS installer > VS instance ellipsis menu > Export configuration). You can compare against yours by exporting and see what's different:

Thanks @LanceMcCarthy I'll compare this list to mine tomorrow. I appreciate you sharing it

We're preparing to make this change in the next few days. We will likely also update to target the Windows SDK version 18362 around the same time as well.

If you want to build on v141 platform toolset on Visual Studio 2019, you have to install Visual Studio 2017 IDE on the same machine, Microsoft does not treat it as a bug, according to a discussion on the vs developer community.

Correct, this isn't a bug, it's just tooling feedback for a smoother developer experience. The easier it is for someone to get started, the higher the likelihood theyll move forward with contributing Heroes 6 download.

@yongyanghz that is not correct for v140/v141 (VS 2015/2017), you can install those components into 2019 without ever installing 2017, as described above.