[
https://issues.apache.org/jira/browse/CB-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157523#comment-16157523
]
Filip Maj commented on CB-13237:
--------------------------------
FYI, on my Windows 10 VM, with VS2017, using SHA {{ab9837b}} of
cordova-windows, adding the {{windows-target-version}} preference you
recommended as a workaround does not work - yields same error. To be fair, my
config.xml is very short:
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns="http://www.w3.org/ns/widgets";>
<preference name="windows-target-version" value="10.0" />
</widget>
{noformat}
I then upgraded to SHA {{94508b8}} and gave it a go:
{noformat}
c:\src\cordova-windows>bin\create ..\wintest2
Creating Cordova Windows Project:
Path: ..\wintest2
Namespace: Cordova.Example
Name: CordovaAppProj
Windows project created with [email protected]
c:\src\cordova-windows>cd ..\wintest2
c:\src\wintest2>cordova\build -d
Searching for available MSBuild versions...
Running command: C:\Windows\system32\reg.exe query
HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\15.0 /v MSBuildToolsPath
Running command: C:\Windows\system32\reg.exe query
HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0 /v MSBuildToolsPath
Running command: C:\Windows\system32\reg.exe query
HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\12.0 /v MSBuildToolsPath
Running command: C:\Windows\system32\reg.exe query
HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0 /v MSBuildToolsPath
Command finished with error code 1: C:\Windows\system32\reg.exe
query,HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0,/v,MSBuildToolsPath
Command finished with error code 1: C:\Windows\system32\reg.exe
query,HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\15.0,/v,MSBuildToolsPath
Command finished with error code 1: C:\Windows\system32\reg.exe
query,HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\12.0,/v,MSBuildToolsPath
Command finished with error code 0: C:\Windows\system32\reg.exe
query,HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0,/v,MSBuildToolsPath
Found MSBuild v4.0 at C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
Using MSBuild v4.0 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
MSBuild v4.0 is not supported, aborting.
c:\src\wintest2\cordova\node_modules\q\q.js:155
throw e;
^
AppPackages doesn't exists
{noformat}
That last line is telling. Inside my previous project, I _do_ have a
{{AppPackages}} directory, but I had to:
1. change the .jsproj file so that the WUR version inside that file matched the
WUR version installed on my Windows machine
2. load the .sln in VS, at which point the Windows 10 project is now
'compatible' (if you skip step 1 above and try to load it in VS, you'll see a
sub-project for each Windows target with a {{(incompatible)}} description text)
3. try to deploy
4. the AppPackages dir gets built.
I'm not sure if this is a separate issue tho - it is filed in CB-12808 I
believe.
> VisualStudio 2017
> -----------------
>
> Key: CB-13237
> URL: https://issues.apache.org/jira/browse/CB-13237
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-windows
> Reporter: Jesse MacFadyen
> Assignee: Jesse MacFadyen
>
> Users who only have VS-2017 and the new tools do not have the expected
> registry items available to 'cordova build' so it fails.
> Failure happens here:
> https://github.com/apache/cordova-windows/blob/a869223824f6ee1a6fc515d4b4aaafc2d8cfba93/template/cordova/lib/build.js#L554
> And the message I saw was 'MSBuild v4.0 is not supported, aborting.'
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
