|
dabriones -15 / 1 / 1 Регистрация: 16.04.2015 Сообщений: 395 |
||||
|
1 |
||||
|
23.05.2016, 18:45. Показов 22540. Ответов 7 Метки нет (Все метки)
Пробую собрать и выдает ошибку:
Файлы: Engine Hack Base 2015.rar
__________________
0 |
|
-15 / 1 / 1 Регистрация: 16.04.2015 Сообщений: 395 |
|
|
24.05.2016, 16:52 [ТС] |
2 |
|
Использовал Microsoft Visual 2012 Добавлено через 21 час 32 минуты
0 |
|
3064 / 1404 / 423 Регистрация: 19.01.2009 Сообщений: 3,828 |
|
|
24.05.2016, 22:19 |
3 |
|
Решениеdabriones, откройте свойства проекта. Во вкладке General есть пункт Platform Toolset, в нем указано v140. Поменяйте его значение на v110 (выбор из выпадающего списка). Жмем Ок. Пробуйем собрать снова.
2 |
|
-15 / 1 / 1 Регистрация: 16.04.2015 Сообщений: 395 |
|
|
24.05.2016, 22:53 [ТС] |
4 |
|
Не наблюдаю такого!
0 |
|
-15 / 1 / 1 Регистрация: 16.04.2015 Сообщений: 395 |
|
|
24.05.2016, 22:55 [ТС] |
5 |
|
0 |
|
dabriones -15 / 1 / 1 Регистрация: 16.04.2015 Сообщений: 395 |
||||
|
24.05.2016, 23:05 [ТС] |
6 |
|||
|
Нашел и толку 0, как исправить?
0 |
|
3064 / 1404 / 423 Регистрация: 19.01.2009 Сообщений: 3,828 |
|
|
25.05.2016, 15:34 |
7 |
|
Решение
v110_xp в выпадающем списке есть v110 без xp? Попробуйте каждый тулсет, который есть у вас в списке. Кстати, что там у Вас?
1 |
|
-15 / 1 / 1 Регистрация: 16.04.2015 Сообщений: 395 |
|
|
25.05.2016, 21:21 [ТС] |
8 |
|
Там не было, но я нашел в другом проекте — Visual Studio 2012 (v110) и всё заработало!
0 |
This is the GitHub page where I’m trying to use msbuild.exe only it’s throwing this following error:
1>------ Build started: Project: keycastow, Configuration: Debug|Win32 ------
C:Program Files (x86)Microsoft Visual Studio2019CommunityMSBuildMicrosoftVCv160Microsoft.CppBuild.targets(379,5): error MSB8020: The build tools for Visual Studio 2013 (Platform Toolset = 'v120') cannot be found. To build using the v120 build tools, please install Visual Studio 2013 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".
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Is there 2 possible options to get this on GitHub to work?
NOTE: I would prefer option number one.
- To update the current code to 2019 standards (would that be difficult for a beginner)?
- Get the current v120 build tools to work.
- Am I missing dependencies for it to work? My current installs View
- I’ve checked this thread here and downloaded Microsoft Build Tools 2013 and installed but I’m having the same problem. Seeing as I’m using 2019, I thought it best to open up a new thread.
Additional info
-
Here’s a screenshot of what I’ve currently installed in Visual Studio 2019.
View. -
There are no options in the current version to install Microsoft Build Tools 2013 in the app itself so the installed standalone version doesn’t appear here as an option.
asked Jun 23, 2019 at 16:21
![]()
2
Open the keycastow.vcxproj with notepad, change here the <PlatformToolset>v120</PlatformToolset> to <PlatformToolset>v142</PlatformToolset> to use the VC++ 2019 platform or change the version via UI
In Visual Studio, in Solution Explorer, open the shortcut menu for
your project (not for your solution) and then choose Properties to
open your project Property Pages dialog box.
In the Property Pages dialog box, open the Configuration drop-down list and then select All Configurations.
In the left pane of the dialog box, expand Configuration Properties and then select General.
In the right pane, select Platform Toolset and then select the toolset you want from the drop-down list (2019 — v142 in your case)
Choose the OK button.
Now you compile the project without installing anything.
answered Jun 23, 2019 at 18:46
![]()
magicandre1981magicandre1981
27.4k5 gold badges83 silver badges124 bronze badges
3
For VS2019, I had to switch from a Visual Studio Build to an MSBuild Build and then specify which MSBuild.exe the build machine would run. The default was from a different PlatformToolset.

Change the Path to MSBuild to the correct MSBuild.exe; e.g.
C:Program Files (x86)Microsoft Visual Studio2019EnterpriseMSBuildCurrentBinamd64MSBuild.exe
answered Apr 5, 2021 at 21:26
![]()
ergohackergohack
1,22014 silver badges26 bronze badges
Got the following error message trying to build a Visual Studio 2022 project
Error MSB8020: The build tools for v143 (Platform Toolset = ‘v143’) cannot be found. To build using the v143 build tools, please install v143 build tools.
Your solution and this one worked for me 🙂
Visual Studio 2022 not listed in devops build solution pipeline task
answered Mar 15, 2022 at 13:45
1
Permalink
Cannot retrieve contributors at this time
| title | description | ms.date | ms.topic | f1_keywords | dev_langs | author | ms.author | manager | ms.technology | ms.workload |
|---|---|---|---|---|---|---|---|---|---|---|
|
MSBuild error MSB8020 |
MSBuild error MSB8020 occurs when the platform toolset required by the build isn’t installed. |
10/29/2021 |
error-reference |
MSB8020 |
C++ |
ghogen |
ghogen |
jmartens |
msbuild |
multiple |
MSBuild error MSB8020
MSB8020: The build tools for toolset-name (Platform Toolset = ‘platform-toolset‘) cannot be found. To build using the platform-toolset build tools, please install toolset-name 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».
To resolve this issue, upgrade the project to use the current Visual Studio toolset, or use the Visual Studio Installer to install the specified build toolset. For more information, see Modify Visual Studio. Use the Individual components tab in the installer to choose specific platform toolsets.
- Remove From My Forums
-
Question
-
Hi,
I am trying to build a solution using MSBuild but I get an error seemingly indicating some tools are not installed. I looked in the directories and they indeed seem to be nowhere found. The message I get is:
C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V140Microsoft.Cpp.Platform.targets(57,5): error MSB8020: The build t
ools for v141 (Platform Toolset = ‘v141’) cannot be found. To build using the v141 build tools, please install v141 bui
ld tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-cli
ck the solution, and then selecting «Retarget solution». [C:UsersJuan DentC++ DevelopmentSource Componentsmetashel
lmetashell3rdtemplightbuildZERO_CHECK.vcxproj]and the MSBuild directory v4.0 only has v110, v120, v140 — not v141!
Thanks,
Juan
Juan Dent
Answers
-
Disable the MSBuild parallel build options?
This will only let MSBuild start one project build at a time.
This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because
the major point of my posts is to aid in the learning process.-
Marked as answer by
Sunday, January 21, 2018 12:26 AM
-
Marked as answer by
- Remove From My Forums
-
Question
-
I got following error building a C++ driver project in the container.
C:Program Files (x86)Microsoft Visual Studio2019BuildToolsMSBuildMicrosoftVCv160Microsoft.CppBuild.targets(3
79,5): error MSB8020: The build tools for WindowsKernelModeDriver10.0 (Platform Toolset = ‘WindowsKernelModeDriver10.0’) cannot be found. To build using the WindowsKernelModeDriver10.0 build tools, please install WindowsKernelModeDriver10.0 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».How to resolve this error? Thanks.
Dockerfile for the container
FROM mcr.microsoft.com/windows/servercore:ltsc2019 ENV TEMP_DIR="c:/temp" SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] # Create temp file for installers RUN New-Item -ItemType Directory -Force -Path $env:TEMP_DIR; # Install VS BuildTools 2019 SHELL ["cmd", "/S", "/C" ] COPY ./BuildTools2019 "$TEMP_DIR/BuildTools2019" RUN C:tempBuildTools2019vs_buildtools_2019.exe --quiet --wait --norestart --nocache --noWeb --add Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools --add Microsoft.VisualStudio.Workload.VCTools --add Microsoft.Net.Component.3.5.DeveloperTools --add Microsoft.VisualStudio.Component.Windows10SDK.17763 --add Microsoft.VisualStudio.Component.Windows10SDK.18362 --add Microsoft.VisualStudio.Component.VC.CMake.Project --add Microsoft.VisualStudio.Component.VC.ATLMFC SHELL ["powershell", "-NoProfile", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; "] RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install WDK 10 1703 COPY ./WDK1703 "$TEMP_DIR/WDK1703" RUN Start-Process -FilePath "$env:TEMP_DIR/WDK1703/wdksetup.exe" -ArgumentList '/q', '/norestart' -PassThru | Wait-Process; RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install WDK 10 1809 COPY ./WDK1809 "$TEMP_DIR/WDK1809" RUN Start-Process -FilePath "$env:TEMP_DIR/WDK1809/wdksetup.exe" -ArgumentList '/q', '/norestart' -PassThru | Wait-Process; RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install WDK 10 1903 COPY ./WDK1903 "$TEMP_DIR/WDK1903" RUN Start-Process -FilePath "$env:TEMP_DIR/WDK1903/wdksetup.exe" -ArgumentList '/q', '/norestart' -PassThru | Wait-Process; RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install VCRedist 2012 COPY ./VCRedist2012 "$TEMP_DIR/VCRedist2012" RUN Start-Process -FilePath "$env:TEMP_DIR/VCRedist2012/vcredist_x64_2012.exe" -ArgumentList '/passive', '/norestart' -PassThru | Wait-Process; COPY ./ABC "c:/ABC"
Answers
-
WDK includes a VSIX package, which contains the Visual Studio extension that integrates Visual C++ with the WDK build .props and .targets.
You need to install the MSBuild .props and .targets included in the VSIX package. Fortunately, you can manually extract the VSIX and copy the contents into Visual Studio. Assuming your VS Build Tools are installed in C:BuildTools2019, you can add the following
commands to your Dockerfile:# Install WDK.vsix manually by extracting its contents. RUN Copy-Item ""${Env:ProgramFiles(x86)}Windows Kits10VsixVS2019WDK.vsix"" 'C:wdkvsix.zip' RUN Expand-Archive 'C:wdkvsix.zip' -DestinationPath 'C:WdkVsix' RUN Copy-Item 'C:WdkVsix$MSBuildMicrosoft*' -Destination 'C:BuildTools2019MSBuildMicrosoft' -Recurse -Force RUN Remove-Item 'C:WdkVsix' -Force -Recurse RUN Remove-Item 'C:wdkvsix.zip' -Force-
Marked as answer by
Wednesday, August 14, 2019 6:58 PM
-
Marked as answer by
- Remove From My Forums
-
Question
-
I got following error building a C++ driver project in the container.
C:Program Files (x86)Microsoft Visual Studio2019BuildToolsMSBuildMicrosoftVCv160Microsoft.CppBuild.targets(3
79,5): error MSB8020: The build tools for WindowsKernelModeDriver10.0 (Platform Toolset = ‘WindowsKernelModeDriver10.0’) cannot be found. To build using the WindowsKernelModeDriver10.0 build tools, please install WindowsKernelModeDriver10.0 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».How to resolve this error? Thanks.
Dockerfile for the container
FROM mcr.microsoft.com/windows/servercore:ltsc2019 ENV TEMP_DIR="c:/temp" SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] # Create temp file for installers RUN New-Item -ItemType Directory -Force -Path $env:TEMP_DIR; # Install VS BuildTools 2019 SHELL ["cmd", "/S", "/C" ] COPY ./BuildTools2019 "$TEMP_DIR/BuildTools2019" RUN C:tempBuildTools2019vs_buildtools_2019.exe --quiet --wait --norestart --nocache --noWeb --add Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools --add Microsoft.VisualStudio.Workload.VCTools --add Microsoft.Net.Component.3.5.DeveloperTools --add Microsoft.VisualStudio.Component.Windows10SDK.17763 --add Microsoft.VisualStudio.Component.Windows10SDK.18362 --add Microsoft.VisualStudio.Component.VC.CMake.Project --add Microsoft.VisualStudio.Component.VC.ATLMFC SHELL ["powershell", "-NoProfile", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; "] RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install WDK 10 1703 COPY ./WDK1703 "$TEMP_DIR/WDK1703" RUN Start-Process -FilePath "$env:TEMP_DIR/WDK1703/wdksetup.exe" -ArgumentList '/q', '/norestart' -PassThru | Wait-Process; RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install WDK 10 1809 COPY ./WDK1809 "$TEMP_DIR/WDK1809" RUN Start-Process -FilePath "$env:TEMP_DIR/WDK1809/wdksetup.exe" -ArgumentList '/q', '/norestart' -PassThru | Wait-Process; RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install WDK 10 1903 COPY ./WDK1903 "$TEMP_DIR/WDK1903" RUN Start-Process -FilePath "$env:TEMP_DIR/WDK1903/wdksetup.exe" -ArgumentList '/q', '/norestart' -PassThru | Wait-Process; RUN dir "$env:TEMP_DIR" | Remove-Item -Force -Recurse -ErrorAction SilentlyContinue # Install VCRedist 2012 COPY ./VCRedist2012 "$TEMP_DIR/VCRedist2012" RUN Start-Process -FilePath "$env:TEMP_DIR/VCRedist2012/vcredist_x64_2012.exe" -ArgumentList '/passive', '/norestart' -PassThru | Wait-Process; COPY ./ABC "c:/ABC"
Answers
-
WDK includes a VSIX package, which contains the Visual Studio extension that integrates Visual C++ with the WDK build .props and .targets.
You need to install the MSBuild .props and .targets included in the VSIX package. Fortunately, you can manually extract the VSIX and copy the contents into Visual Studio. Assuming your VS Build Tools are installed in C:BuildTools2019, you can add the following
commands to your Dockerfile:# Install WDK.vsix manually by extracting its contents. RUN Copy-Item ""${Env:ProgramFiles(x86)}Windows Kits10VsixVS2019WDK.vsix"" 'C:wdkvsix.zip' RUN Expand-Archive 'C:wdkvsix.zip' -DestinationPath 'C:WdkVsix' RUN Copy-Item 'C:WdkVsix$MSBuildMicrosoft*' -Destination 'C:BuildTools2019MSBuildMicrosoft' -Recurse -Force RUN Remove-Item 'C:WdkVsix' -Force -Recurse RUN Remove-Item 'C:wdkvsix.zip' -Force-
Marked as answer by
Wednesday, August 14, 2019 6:58 PM
-
Marked as answer by
Содержание
- Visual studio error msb8020 the
- Answered by:
- Question
- Answers
- All replies
- Visual studio error msb8020 the
- Asked by:
- Question
- Visual studio error msb8020 the
- Asked by:
- Question
- All replies
- Visual studio error msb8020 the
- Asked by:
- Question
- All replies
- Visual studio error msb8020 the
Visual studio error msb8020 the
![]()
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:

Question


I got following error building a C++ driver project in the container.
C:Program Files (x86)Microsoft Visual Studio2019BuildToolsMSBuildMicrosoftVCv160Microsoft.CppBuild.targets(3
79,5): error MSB8020: The build tools for WindowsKernelModeDriver10.0 (Platform Toolset = ‘WindowsKernelModeDriver10.0’) cannot be found. To build using the WindowsKernelModeDriver10.0 build tools, please install WindowsKernelModeDriver10.0 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».
How to resolve this error? Thanks.
Dockerfile for the container
Answers


WDK includes a VSIX package, which contains the Visual Studio extension that integrates Visual C++ with the WDK build .props and .targets.
You need to install the MSBuild .props and .targets included in the VSIX package. Fortunately, you can manually extract the VSIX and copy the contents into Visual Studio. Assuming your VS Build Tools are installed in C:BuildTools2019, you can add the following commands to your Dockerfile:


WDK includes a VSIX package, which contains the Visual Studio extension that integrates Visual C++ with the WDK build .props and .targets.
You need to install the MSBuild .props and .targets included in the VSIX package. Fortunately, you can manually extract the VSIX and copy the contents into Visual Studio. Assuming your VS Build Tools are installed in C:BuildTools2019, you can add the following commands to your Dockerfile:


First all there is no WDK.visx file under container directory.
So I copied WDK.visx from my Win 10 system.
Here is the code change made for dockerfile.
And the manually installed VSIX package does not resolve the problem, I got a new error:
BTW, when I using the build Tools 2017, there is no need to install VSIX package, and the C++ driver projects can be compiled without problem, why we need to do this for build Tools 2019?


It sounds like the WDK wasn’t installed correctly if you say that you couldn’t find the VSIX file, nor MsBuild cannot find WindowsDriver.Common.targets.
First, check that the file «C:Program Files (x86)Windows Kits10buildWindowsDriver.Common.targets» exists indeed in your container. If it doesn’t, then it means there was a problem with your WDK installation. I’d review the logs at «%TEMP%wdk» in the container to try to find what went wrong.
Also, I’m not sure what’s the reason you didn’t hit the error with BuildTools 2017, as it should had required the VSIX installed, too. The files provided by the package are required in order for VS to be able to find the required WDK MsBuild files for building driver projects.
Источник
Visual studio error msb8020 the
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
![]()
Asked by:

Question


I am Trying to build a project, I can’t build C++ projects that were created in Visual studio 2013 or 2015, I get this Error:
Error MSB8020 The build tools for v141 (Platform Toolset = ‘v141’) cannot be found. To build using the v141 build tools, please install v141 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». Project name C:Program Files (x86)Microsoft Visual Studio2017CommunityCommon7IDEVCVCTargetsMicrosoft.Cpp.Platform.targets 57
After installing Visual Studio 2017 RC I got a message that the windows 10 SDK wasn’t installed: [0cfc:001f][2016-12-09T04:19:02] Package ‘Win10SDK_10.0.14393.33,version=10.0.14393.3300’ failed to install. Command executed: «C:ProgramDataMicrosoftVisualStudioPackagesWin10SDK_10.0.14393.33,version=10.0.14393.3300packagesWin10SDK10.0.14393.33sdksetup.exe» /features OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart /OriginalSource «C:VS2017packagesWin10SDK10.0.14393.33sdksetup.exe», Return code: 15605, Details: There was a problem downloading your product.
I was installing VS from an ISO image that i’ve downloaded while connected with a cable to the router (tried to eliminate WIFI issues). Is the Win 10 SDK related to the C++ tools? how can I get it to build?
I have uploaded the logs of my Visual Studio installation, here they are: https://1drv.ms/u/s!ArdaoXN9TFnsao8uvnWxXLEuyIg
I have to solve this issue ASAP, I was installing windows 7 and 10 and visual studio 2015 and 2017 and trying repairs for 10 days.
Источник
Visual studio error msb8020 the
![]()
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:

Question


Recently, I installed visual Studio 2015 and tried to build the projects. However, I am getting the following error.
The build tools for v120 (Platform Toolset = ‘v120’) cannot be found. To build using the v120 build tools, please install v120 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».
C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V140Microsoft.Cpp.Platform.targets
FYI, I used to build the projects in visual studio 2013 and for long time, I never used it. But when I updated the visual studio to 2015 version, I am getting this error. Please let me know the solution.
I have tried to re-target the solution and installed v120 MSBuild tools. However, nothing was able to resolve the issue.
Please tell me how to resolve it.


Welcome to MSDN forum.
Since your project was created by Visual Studio 2013, when you build it with Visual Studio 2015, you should change the platform toolset: Visual Studio 2013(v120).
Right click project->Properties->Configuration Properties->General->Platform Toolset, select Visual Studio 2013(v120).
MSDN Community Support Please remember to click Mark as Answer. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
- Edited by Leo Liu-MSFT Microsoft contingent staff Tuesday, October 31, 2017 6:57 AM
- Proposed as answer by Leo Liu-MSFT Microsoft contingent staff Thursday, November 2, 2017 6:55 AM


This however could not address my issue. But I got resolved after searching in google and found that I need to run installer and selected few components to install which addressed my issue.
However, I am getting another error while compiling the code as shown below:
Building an MFC project for a non-Unicode character set is deprecated. You must change the project property to Unicode or download an additional library.
I followed the link below which could not address the issue.
I have also tried to change the character set to Unicode Character Set via Project Properties->Project Defaults. This also could address the issue.


@SomuDhabadi, since you could address your previous issue, you can mark it as answer if it help you. so it could help other community members who get the same issues and we could close this thread.
Besides, since this forum is about the MSBuild, as your later issue is more related to the C++ and MFC, I could not give a directly answer for that issue, but I would like provide you the info what I have know.
The error message is telling you the problem: «Building an MFC project for a non-Unicode character set is deprecated. You should change the project property to Unicode or download an additional library. If possible, you can check below link:
If this still not resolve your issue, I suggest you can open a new thread with more detail info.
Источник
Visual studio error msb8020 the
![]()
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:

Question


I am trying to run the skeleton code of a project in VS 2013. I have both VS 2017 and VS 2013 on my laptop. But since the code is compatible with 2013 Version I downloaded that version. Both of them are community versions. Technically I shouldn’t face any issues with the code, but the error is being shown.


Thank you for posting in MSDN forum.
Although the code is compatible with VS 2013, you could not use build tools V141 in this VS version, please refer to a similar issue as can not use build tools v141 in Visual Studio 2015.
That because v141 is not recognized by Visual Studio 2013. Basically, the software is backward-compatible but not upward-compatible. so when you have multiple versions of build tools installed, the h igh version of VS can use a low version of the build tool, however, the l ow version of VS could not use high-level build tool. That the reason why you get that error.
In order to use v141 build tools, you could use VS 2017 to update your project.
Besides, if you still want to build your project with VS 2013, you have to update your scripts to Visual Studio 2013, only copy the source code to VS 2013 and re-compile.
Источник
Visual studio error msb8020 the
Please try this:
1. Right click your project
2. Click that «Unload project» option
3. Edit your project
4. Check the following setting:
Since the build process will only followed the settings here, I suspect the problem is pending on the value haven’t been updated here.
Or is it possible that your Visual Studio 2012 haven’t installed all Visual Studio Updates?
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.


Thanks for your answer.
We did all the steps mentioned above, PlatformToolset is correctly set to v110_xp, as expected, (v120 is for Visual 2013).
Also, we have all the updates installed, still, we are having the same problem.
C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V110Microsoft.Cpp.Platform.targets(42,5): error MSB8020: The builds tools for Visual Studio 2010 (Platform Toolset = ‘v100’) cannot be found.
Is there any registry key, local files or any other thing that is used to store some build settings configuration other than vcxproj file ?


Then may I ask your project type?
Based on MSDN it is related to vcxproj file:
And the VC++ project Compatibility info:
«You can use Visual Studio 2012 to open a C++ project that was created in Visual Studio 2010 SP1. If you want to use the Visual Studio 2012 build environment to build a project that was created in Visual Studio 2010 SP1, you must have both versions of Visual Studio installed on the same computer. For more information, see How to: Upgrade Visual C++ Projects to Visual Studio 2012 .»
I guess that your project may haven’t converted in the right way? Please check whether you have choosed to update your project when the upgrade wizzard poped out?
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
Источник
Symptom
You have created a Unity project to create an app using MRTK2, and you want to use the new IL2CPP back-end. You open the solution in Visual Studio 2019, you try to deploy it by using Build/Deploy, and all the way at the end, the compiler complains about the «CL.exe» missing.
Alternatively, you might get the slightly more verbose error:
«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».»
Cause
You have most likely used the recommended Unity version (2018.4.2f1) to create the project. This version — the name gives it away — was released before Visual Studio 2019, and therefore, it assumes the presence of Visual Studio 2017 and it’s accompanying C++ tools set, ‘V141’. So, Unity generated a C++ solution referencing that toolset.
But now it’s 2019, you have kissed Visual Studio 2017 goodbye and installed Visual Studio 2019. And that comes with the toolset V142.
Either you install V141 using the Visual Studio Installer, or you tell the generated solution to use V142. I personally prefer the last one, because newer is always better, right?
Simply right-click the project in the solution that has «(Universal Windows)» behind its name, select properties, tab general, and then the problem is already pretty evident:

Simply select Visual Studio 2019 (142) for the Project Toolset and you are good to go. This setting will stay as long as you don’t delete the generated project — Unity will simply change what needs to be changed, and leave as much as it can (to speed up the generation process).
Conclusion
While this was a simple fix, it can be hard to find. Hence, a simple blog about it.
Hope you learned something!
Locate (Unix)
unity
Build (game engine)
Game engine
IT
app
Installer (macOS)
Property (programming)
Blog
Сообщение было отмечено BRcr как решение
