-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have 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
error MSB8020: The build tools for v140 (Platform Toolset = 'v140') cannot be found #60
Comments
Hi, I fixed this issue by installing VS 2015 Update 3 and select option UWP Tools during installation. The thing is I'm using VS 2017, I don't need VS 2015 which takes 15 Gb after installation. I tried the other methods to install v140 build tools separately to save disk space such as installing the VC++ 2015.3 toolset, but no luck. I referred to this site which says that I need VS 2015 Update 3 installed and it really fixed this issue. But it doesn't make any sense to install a massive VS 2015 IDE to fix an issue. Is there any better solution to fix this issue without installing VS 2015? Thanks. |
Thanks @tuanbs that looks like the correct workaround. This plugin version will be updated to use build tools v141 in the near future. Marked as a bug. |
Thanks @brodybits to take it into account. Hope it could be fixed ASAP as it doesn't make sense to fix it by installing the massive VS 2015 (which takes space of more 10 Gb) while using VS 2017. |
This plugin version is now updated to support VS 2017 with v141 build tools, workaround to use old build tools (v140) in VS 2017 is no longer needed. Thanks @tuanbs for your patience. |
Hi, I got the following error when building the app for windows platform on Windows 10 using VS 2017 community:
It works fine with iOS and Android platforms. I can build and run the sample side-menu template of Ionic 1 framework with Windows platform. But when I added this plugin it raised the above error. I followed the section 'Windows platform notes' but still no luck.
The text was updated successfully, but these errors were encountered: