You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by ja...@apache.org on 2018/03/05 12:10:25 UTC
[cordova-docs] branch master updated: fix word jumble in windows
release post
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cordova-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 582f6b9 fix word jumble in windows release post
582f6b9 is described below
commit 582f6b928498f85a1621e69b25df7bf4fd755e39
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Mon Mar 5 13:10:23 2018 +0100
fix word jumble in windows release post
---
www/_posts/2018-02-27-cordova-windows-6.0.0.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www/_posts/2018-02-27-cordova-windows-6.0.0.md b/www/_posts/2018-02-27-cordova-windows-6.0.0.md
index 4c9dbbe..ff24a99 100644
--- a/www/_posts/2018-02-27-cordova-windows-6.0.0.md
+++ b/www/_posts/2018-02-27-cordova-windows-6.0.0.md
@@ -17,7 +17,7 @@ This is a major release that changes functionality you might rely on, so please
- **Windows 10 / UWP** builds are now default, meaning `cordova build windows` will now build a Windows 10 UWP app by default.
Windows (Phone) 8.1 is still supported, of course, just use `cordova build windows -- --appx=8.1-win`, `cordova build windows -- --appx=8.1-phone` or an equivalent configuration option.
- You can now build apps with a current installation of **Visual Studio 2017** (`15.5.x` at the time of writing) without any additional configuration or hacks (like the environment variable `VSINSTALLDIR` that was required for 5.0.0). (Note: [Visual Studio 2017 doesn't support Windows 8.1 apps anymore](https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2017-compatibility-vs#windows-store-and-windows-phone-apps), so you can only build these apps with Visual Studio 2015 installed.)
-- New **ENV variable `MSBUILDDIR`** allows to directly configure the MSBuild Tools to be used to build the app. While `VSINSTALLDIR` always has been a hack that accidentally also worked to switch between different MSBuildTools versions, we now we this functionality explicit: Just set the ENV var to a your desired MSBuild folder (e.g. `C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin` or `C:\Program Files (x86)\MSBuild\14.0\bin\`) and it will be used to buil [...]
+- New **ENV variable `MSBUILDDIR`** allows to directly configure the MSBuild Tools to be used to build the app. While `VSINSTALLDIR` always has been a hack that accidentally also worked to switch between different MSBuildTools versions, we now make this functionality explicit: Just set the ENV var to a your desired MSBuild folder (e.g. `C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin` or `C:\Program Files (x86)\MSBuild\14.0\bin\`) and it will be used to bui [...]
- If you have Visual Studio 2017 and Visual Studio 2015 installed at the same time, the normal logic would always choose Visual Studio 2017's MSBuild 15 - and fail on a Windows (Phone) 8.1 project. If you set the environment variable to MSBuild 14, it can successfully build your 8.1 apps.
- If the supplied path is invalid or doesn't contain a working MSBuild, the normal MSBuild selection logic will be triggered
- Fixes several bugs
--
To stop receiving notification emails like this one, please contact
janpio@apache.org.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org