[ 
https://issues.apache.org/jira/browse/CB-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Grebnov updated CB-6039:
-------------------------------

    Assignee: Jesse MacFadyen  (was: Sergey Grebnov)

> [windows8] Add test that correct msbuild version is in the path
> ---------------------------------------------------------------
>
>                 Key: CB-6039
>                 URL: https://issues.apache.org/jira/browse/CB-6039
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI, Windows 8
>            Reporter: Sergey Grebnov
>            Assignee: Jesse MacFadyen
>
> 1. Test for msbuild is in the path was removed as part of CB-5359 fix.
> Due to this in case of msbuild command is NOT in the path 'cordova build 
> windows8' reports success, but no build artifacts are produced. Must be fixed.
> 2. We don't officially support windows8.1 project template, but it is 
> possible to upgrade your project file 
> (.cordova\lib\windows8\cordova\3.x.x\windows8\template) so that cordova 
> produces windows81 application instead of windows8. In this case msbuild 
> tools v12 (comes with Visual Studio 2013) must be used instead of v4.0 (see 
> below).  So build command must recognize if msbuild version in the path does 
> not match target template and report this to user.
> New Visual Studio 2013 comes with new MS Build tools v12.
> > msbuild /ver
> Microsoft (R) Build Engine version 12.0.21005.1
> [Microsoft .NET Framework, version 4.0.30319.34003]
> Copyright (C) Microsoft Corporation. All rights reserved.
> 12.0.21005.1
> But windows8\bin\check_reqs.js fails since it expects the following output
> >msbuild /ver
> Microsoft (R) Build Engine version 4.0.30319.33440
> [Microsoft .NET Framework, version 4.0.30319.34003]
> Copyright (C) Microsoft Corporation. All rights reserved.
> If I remove this check for particular msbuild version cordova-cli can 
> successfully create windows8 template and then build it using MSBuild v12.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to