You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by GitBox <gi...@apache.org> on 2018/08/15 05:53:15 UTC

[GitHub] shazron commented on issue #274: MSBuild v4.0 Not supported and possibly why all these other MSBuild issues are happening.

shazron commented on issue #274: MSBuild v4.0 Not supported and possibly why all these other MSBuild issues are happening.
URL: https://github.com/apache/cordova-windows/issues/274#issuecomment-413101021
 
 
   See http://www.visualstudioextensibility.com/2016/11/23/some-implications-of-the-new-modular-setup-of-visual-studio-2017-for-vsx-developers/ :
   
   ```
   The location of MSBuild for VS 2017 has changed, and can be several of them.
   In the past (until Visual Studio 2015), the path of MSBuild was “C:\Program Files (x86)\MSBuild\<version>”, where <version> was “4.0”, “12.0” (VS 2013), “14.0” (VS 2015). 
   
   There is no “15.0” folder there for VS 2017. Instead, MSBuild for VS 2017 is installed in the folder “C:\Program Files (x86)\Microsoft Visual Studio\2017\<edition>\MSBuild\15.0”, where edition can be “Community”, “Professional” or “Enterprise”. 
   
   Again, for your own use on your own build script you can hardcode the path, but if you want to use a more proper way, you need to get the VS 2017 installation folder as explained above and concatenate “MSBuild\15.0”. 
   
   Or you can wait until Microsoft releases a document about how to resolve MSBuild location (they are working on it and now that MSBuild is open source you can follow the progress on GitHub). BTW, you can download the MSBuild Tools for Visual Studio 2017 RC here.
   ```
   
   So, to have auto-detect working properly we need to add more locations to check as per the article, and only rely on the registry as a fallback. I had VS 2017 Community installed, and it only detected MSBuild v4 from the .NET Framework so I had to use the MSBUILDDIR env var.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org