Bonus point: we will already have agents set up when the app will really migrate to v14. 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). If possible, create an extra build-agent modifying all.Once decided, indicate the migration date minimum 2 weeks before in README.md + a pinned message in the Issues tab.add a paragraph or a link in README.md explaining how to install 14.1 build tools with VS2019.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.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.Not all extensions and plugins are ported for the moment, it can be an issue for accessibility.The Visual Basic and C compilers are also included in this download. NET Framework, but they are now available as this separate download. These tools previously were included in the. IT will need some time to test, whitelist, package and deploy VS2019. If you don't already have Visual Studio installed on your computer, Microsoft Build Tools 2015 provides the essential tools for building managed applications.Visual Studio has always some stability issues with first versions, including 2019 (see dev forums + some mailing-lists 😉).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).I agree with I would recommend to wait a little (and a couple of VS updates) before really migrating, sorted by importance: This can be mitigated by making sure v141 is still in the list after adding v142. This may affect developers who have not updated to Visual Studio 2019 yet if there's no backwards check in the toolcheck list. VS2019 is significantly faster to use than VS2017 (this is proven, not just anecdotal).Stay in sync with Microsoft's vision of using modern tooling.The default toolset version will be preselected as v142 by default.

Open the Solution in Visual Studio 2019 and right click on the solution head.Retarget the solution, which is literally a two-click process: => You are not able to build, due to failed checks for the v141 Toolset Clone this repo with only Visual Studio 2019 installed.

Note: those Build Tools can be quickly found here.

These can be hard to find for the everyday dev, requiring you to go to MSDN downloads and search specifically for the required version. Retarget the solution to VS2019 Build tools (v142) to allow support for Visual Studio 2019, out-of-the-box.ĭevelopers cannot use Visual Studio 2019 to build this solution without installing older Visual Studio 2017 Build Tools (v141).

Platform toolset 141 download