You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: