Visual Studio 2013 Error Ms8020 Build Tools V140 Cannot Be Found

Visual Studio 2013 error MS8020 Build tools v140 cannot be found

That's the platform toolset for VS2015. You uninstalled it, therefore it is no longer available.

To change your Platform Toolset:

1. Right click your project, go to Properties.
2. Under Configuration Properties, go to General.
3. Change your Platform Toolset to one of the available ones.

Visual Studio 2013, error MSB8020: The build tools for Visual Studio 2010 cannot be found

So the thing you're missing here is that FireBreath projects are built using CMake -- the actual contents of the build directory should always be completely temporary and never stored in source control. To build the project on a new computer you need to run the prep command again from scratch.

If the previous maintainer changed the build files manually and/or migrated it to a newer version of visual studio without using cmake to do it then they did some very ugly things and all bets are off... good luck.

This is why all the firebreath documentation (I wrote most of it) strongly urges that the build directory be transient and you always do project file updates in cmake.

Hope that helps!

Visual Studio 2019 - error MSB8020: The build tools for Visual Studio 2013 cannot be found

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.

1. In the Property Pages dialog box, open the Configuration drop-down list and then select All Configurations.

2. In the left pane of the dialog box, expand Configuration Properties and then select General.

3. In the right pane, select Platform Toolset and then select the toolset you want from the drop-down list (2019 - v142 in your case)

4. Choose the OK button.

Now you compile the project without installing anything.

Visual Studio 2013 Professional error MSB8020

You need to change the target toolset for your project (more information here). Generally newer toolset versions cannot be used in older Visual Studio versions, however, older toolsets can be used in newer Visual Studios. So, you need to set the toolset to the oldest version you will be using.

Go to the project properties for your project, and in the General tab, change the Platform Toolset to Visual Studio 2013 (v120), and your project should work in both VS2013 and VS2015.

The build tools for v140 cannot be found

If msbuild still complains about v140, this likely means v140 is still in the project file - which you can verify with a text editor.
Are you sure you changed the toolset for all platform/configuration combinations? For instance if you just open the settings dialog and it happens to be showing properties for Debug|Win32 and you change one of those, but then you build Release|Win32, the latter combination will still use v140. Open the proprties dialog again and verify all platforms and configurations use the correct toolset. Or use find/replace from v140 -> v120 in a text editor

error MSB8020: The build tools for v141 (Platform Toolset = 'v141') cannot be found when trying to install npm module scrypt

After a few more hours, i found out there was an old installation of visual studio 2015. I had to uninstall it first. I have no clue, why not the newest instance of build tools was used.

After this, and downgrading Node to v8, scrypt could be installed and compiled again.

Building Visual Studio 2015 C++ project (v140) by MSBuild Failed - v140 cannot be found

Your problem is that you set the environment variable VisualStudioVersion to 12.0. This tells MSBuild to use the Visual Studio 2013 (V120) tools, which don't support the Visual Studio 2015 (V140) build tools. If you unset this environment variable, or pass the /p:VisualStudioVersion=14.0 option to MSBuild your project, should build. (Or at least get past this error).

You can find more information about the VisualStudioVersion variable in a MSDN blog entry titled Visual Studio project compatibility and VisualStudioVersion.

---

Related Topics