Skip to content

nuget: don't try to find msbuild (incorrectly) #1458

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 14, 2017

Conversation

ethomson
Copy link
Member

With the changes in the way MSBuild is bundled and installed in Visual
Studio 2015+, we can no longer use the old hacky way to find where
msbuild is installed.

This busted AppVeyor whose image has VS 2015 installed and an old
(incompatible) version of msbuild installed elsewhere. We would find
only the old version.

Require nuget package users to have msbuild in their path.

With the changes in the way MSBuild is bundled and installed in Visual
Studio 2015+, we can no longer use the old hacky way to find where
msbuild is installed.

This busted AppVeyor whose image has VS 2015 installed and an old
(incompatible) version of msbuild installed elsewhere.  We would find
only the old version.

Require nuget package users to have msbuild in their path.
@ethomson ethomson merged commit 493b576 into master Jun 14, 2017
@ethomson ethomson deleted the ethomson/nuget_msbuild branch February 15, 2019 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant