Retrieve msbuild path form the registry instead of having a static VS… #759
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…2017 community version msbuild path Using the following solution: https://stackoverflow.com/a/43623213/573208
|
Thanks for that! It's always good to make it easier for people to get involved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently MSBuild path is typed statically and Visual studio 2017 community edition is used for that purpose. For those running other versions of VS the build results in an error and requires you to manually edit the build.ps1 file.
I have added a Get-MSBuild-Path (https://stackoverflow.com/a/43623213/573208) to dynamically retrieve MSBuild path during the build process.