5/26/2023 0 Comments Visual studio 2019 build tools![]() 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.IT will need some time to test, whitelist, package and deploy VS2019.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.
0 Comments
Leave a Reply. |