Skip to content
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

Local nuget.exe should take precedence over NuGet on PATH (follow-up #702) #717

Closed
mthierba opened this issue Mar 30, 2015 · 1 comment
Closed

Comments

@mthierba
Copy link

I absolutely agree with #702 that NuGet.exe should be searched in the PATH, but the way how this has been implemented in f83255d, it has now broken several of my CI builds (had the latest NuGet in "./packages", but an older one installed globally), and I have a feeling this might be the case for others, too.

I think NuGet should be looked for locally first, and only in the PATH as a fall-back. Other tools like npm work the same way, so most users come with that expectation, and would find the new behavior counter-intuitive.

@forki
Copy link
Member

forki commented Mar 30, 2015

Oh this was absolutely unintended. Can you please submit a pull request then I will release the fix as soon as possible. Sorry

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

No branches or pull requests

2 participants