Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
6
Found in
2018.4.0f1
2019.1.0a10
2019.1.8f1
2019.2.0a1
2019.3.0a1
Issue ID
1166131
Regression
No
[UWP] Building project for Visual Studio 2019 generates solution that targets build tools for VS 2017 tool-set (v141)
How to reproduce:
1. Have a system with Visual Studio 2019 and no Visual Studio 2017 and no MSVC v141
2. Create a new project or open existing one
3. In Build Settings, switch target platform to UWP
4. Verify "Visual Studio Version" field is set to "Visual Studio 2019" or "Latest installed" and that no other Visual Studio version is listed
5. Build the project
6. Open the newly build Visual Studio Solution (with Visual Studio 2019)
7. Build on Local Machine with Debug|x64 options
-- Building process fails with an error that the build tools for Visual Studio 2017 (v141) cannot be found. (exact error message below)
Expected result: When "Visual Studio 2019" or "Latest installed" option is selected (step 4), step 5 should generate a solution that targets Platform Toolset v142 without the need to manually Retarget Solution in Visual Studio.
Actual result: Building project for "Visual Studio 2019" generates a solution that targets build tools for Visual Studio 2017, therefore, it is needed to manually Retarget Solution in Visual Studio.
Reproducible with - 2018.4.3f1, 2019.1.0a10, 2019.1.9f1, 2019.2.0a1, 2019.2.0b8, 2019.3.0a8
Note: Not tested on 2017.4.29f1, 2019.1.0a1-a9 and since VS 2019 installation is not detected on those versions.
Exact error message:
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". New Unity Project (2) C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppBuild.targets 379
-
true_warlock
Oct 13, 2020 02:23
I cant even use Unity right now with Visual studios even after doing steps like tracking down the C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE devenv.exe bit, and so on. Wont find nothing. the installation process is simply busted and I am seeing no fixes in sight. Tried to see if updating to latest 2020 version mix help. This is very annoying and waiting for a maybe fix isn't going to work for most of us. We need answers please.
-
CyberAngel
Oct 07, 2019 12:03
Not fixed in 2019.2.8 so how do we fix this issue?
-
eprovencher
Aug 23, 2019 14:12
For me, the build fails even when retargetting for v142 build tools.
-
ddayptc
Aug 08, 2019 13:58
If you have v141 of the toolset another symptom is that the Device option does not show up in studio for debugging on the Hololens
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a4
Backported to 2018.4.10f1, 2019.2.6f1, 2019.3.0b4