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
{{ message }}
This repository has been archived by the owner on Mar 18, 2018. It is now read-only.
Not really feasible with vanilla NuGet. Current solution is an easy one-liner when installing the package. For it to detect the path would probably be a lot more hassle. Although I might be wrong, you're always welcome to submit a pull request with the proposed fix.
You could also take a look at the excellent Paket dependency manager. Just discovered this myself a week ago when playing around with F#. It creates a directory hierarchy where the NuGet package version isn't in the path name. Thus its easy to upgrade the package without having to modify the .csproj files.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the csproj:
This is great until the package is upgraded and then the line needs to be changed. This version number should track the version in use by the project.
The text was updated successfully, but these errors were encountered: