[TIMOB-24569] Windows: Add support for Visual Studio 2017 (26403.03)
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2017-08-21T09:57:21.000+0000 |
Affected Version/s | Release 6.1.0 |
Fix Version/s | Release 6.2.0 |
Components | Windows |
Labels | n/a |
Reporter | Gary Mathews |
Assignee | Kota Iguchi |
Created | 2017-04-10T14:41:19.000+0000 |
Updated | 2017-08-22T09:29:39.000+0000 |
Description
It's possible for
vsInfo.vsDevCmd
to use the long path with spaces C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\VsDevCmd.bat
instead of the short path 'C:\\PROGRA~2\\MICROS~2\\2017\\COMMUN~1\\Common7\\Tools\\VsDevCmd.bat'
.
This prevents spawn
from executing VsDevCmd.bat
.
[~gmathews] Did you get any error output when you use long path? I was not able to reproduce the issue, originally the reason because we are using long path for
vsDevCmd
is that I have been seeing some VS batch tools includingvsvarsall
didn't work correctly when you use short path. I am suspecting there has been changes at some point of Windows 10 SDK update...I am not able to build Titanium app with latest Visual Studio 2016 (26403.03). For me build fails at CMake, it seems it doesn't create project files correctly. I tried latest CMake (3.8.0). We might want to check out CMake nightly build.
I was able to make this work again by * Uninstall Visual Studio 2017, and then re-install it using [latest installer](https://www.visualstudio.com/thank-you-downloading-visual-studio/?sku=Community&rel=15). * Then setting target platform version to
10.0.10586.0
other than10.0.15063.0
https://github.com/appcelerator/titanium_mobile_windows/pull/959
Backported in https://github.com/appcelerator/titanium_mobile_windows/commit/32661af33f5238c8fad24bdef268c326aa4ad705
Verified changes in 6.2.0.v20170821203442