Platform Toolset 141 Download
- Install Platform Toolset 141
- Platform Toolset 141 Download Windows 10
- Platform Toolset 141 Download For Mac
- Platform Toolset V140
Join GitHub today
The builds tools for v140 (Platform Toolset = 'v140') cannot be found Project file contains ToolsVersion='14.0' (.) Treating the project as if it had Tools. The Windows Driver Kit (WDK) takes advantage of the MSBuild platform toolset feature to provide tools and libraries that are specific to driver development. The MSBuild platform toolset feature is extensible. The specific version of the platform toolset that you want to use is controlled by an MSBuild property called PlatformToolset.
Update msi laptop drivers. GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Jul 10, 2015 If you don't already have Visual Studio installed on your computer, Microsoft Build Tools 2015 provides the essential tools for building managed applications. These tools previously were included in the.NET Framework, but they are now available as this separate download. The Visual Basic and C# compilers are also included in this download.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Install Platform Toolset 141
commented Feb 19, 2018 • edited
edited
Hosted 2017 ought to support the v141 toolset, but it appears only v140 is installed: Can we get v141 installed on Hosted 2017? |
commented Feb 19, 2018
The hosted image is updated on a monthly basis pulling the latest VS. So when VS updates to 141, the next monthly image will carry it. |
commented Feb 19, 2018 • edited
edited
This was working in my CI release on 2-1, the last time I checked in to my project. I queued a CI build today and it fails with this error. Clearly the hosted 2017 image DID have v141 and now it does not. Do we know which checkin broke this and which one will be fixing it? Further - I checked my nightly builds, which are apparently not running nightly. But the build on 2/6 succeeded. The build on 2/13 failed. So the break happened some time in there |
commented Feb 19, 2018
@stephenegriffin - thanks. As a guess, I would say VS updates ran in one case and in the other it didn't. But that's just a guess. We will investigate. VS Updates shouldn't run once the image is provisioned into the pool. Nothing changed in the install script so this is something dynamic: https://github.com/Microsoft/vsts-image-generation/commits/master/images/win/scripts/Installers/Vs2017/Install-VS2017.ps1 |
commented Feb 20, 2018
Platform Toolset 141 Download Windows 10
So - I was digging a bit more on this. I found the Agent Queues which shows me which pools my builds are queuing in. Despite having the default queue of Hosted VS2017 selected on my build definitions, it looks like all of my builds are queuing in Hosted instead. That explains the lack of capabilities. But something is definitely wrong with how my agents are being selected. There's still a bug here, but now I don't know where it is. |
commented Feb 20, 2018
I have filed this: https://developercommunity.visualstudio.com/content/problem/200822/hosted-vs2017-builds-queuing-in-hosted-agents.html |
Platform Toolset 141 Download For Mac
commented Feb 23, 2018
Closing this issue since it's unrelated image-generation process. |
commented Jul 13, 2018 • edited
edited
Platform Toolset V140
It appeared to me, that the reason for the problem was a not needed VCTargetsPath system variable. After removing it, VS 2017 now sees V141 toolset. |