Question: Is there a way to force to get latest version of nuget?
See original GitHub issueHi
Is there an option in the #load "nuget:package.name, 1.0.0"
notation to force to get the latest version. It seems as if I put *
as the version, it always takes the ‘first’ version. For example, I have a 1.0.0
and a 1.0.1
. When I run it will always take 1.0.0
if I specify *
as version.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:18
Top Results From Across the Web
nuget spec dependencies, get latest version?
A recommended way is to run NuGet.exe Restore command first before running the Update command. Share.
Read more >Reference latest version of nuget package using ...
Is there any way to force nuget to always take the latest available version of a nuget package?
Read more >Reinstalling and Updating NuGet Packages
Updating a package simply means installing an updated version, ... For all packages, delete the package folder, then run nuget install .
Read more >Best way to automatically get latest version of dependent ...
To update an individual package, use nuget install without specifying a version number, in which case NuGet installs the latest version. Upvote
Read more >c# - Policies on NuGet dependencies versions when ...
To follow up with my solution: I take dependency on all the latest versions of the libraries I need, NuGet package I produce...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes
I will follow up on this one and create a test case the coming days. What I had was, I created a new package 1.0, used that in the script, next, I created an update on the package 1.1, and ran the same script again. Then it just used the 1.0 package all the time. I will try to replicate that scenario.