support for bulk-updating references into csproj from commandline(s)

[rrelyea]

splitting off from #3751 - which now just covers the add side of this work

Spec draft: https://github.com/NuGet/Home/wiki/Support-dotnet-ref-add%7Cupdate%7Cdelete-packageref

nuget.exe update for package reference

[rrelyea]

since add will support "update", we'll prioritize this task as the lowest of the 4:

1. add 2) remove 3) list 4) update

[dasMulli]

Would it make sense to allow updating all package references? For a lot of dependencies, it is very quick to do sth like dotnet update pkg --all to begin with when updating a project.

[kjbetz]

I would highly suggest checking out how yarn has taken care of this with yarn upgrade and yarn upgrade-interactive

https://yarnpkg.com/lang/en/docs/cli/upgrade/

https://yarnpkg.com/lang/en/docs/cli/upgrade-interactive/

I would just use the same names as well... dotnet upgrade dotnet upgrade-interactive or possibly dotnet package upgrade dotnet package upgrade-interactive

[rrelyea]

Notice that #6193 added the additional requests to support cross-project updates, etc...

[mudrz]

Since this issue is 2 years old - are there any plans to create any basic cli commands for managing package versions?
Currently it is very inconvenient to manage packages outside of Visual Studio on Windows.

[letmaik]

As part of continuous integration I'd like to auto-update dependencies to check that nothing breaks with newer versions. However, this seems impossible without this feature if you manage your dependencies in .csproj files. Any ETA for this? It seems like a basic feature to have.

[mishra14]

@letmaik you can always run dotnet add package <package_name>. This command will find the latest version of the package and update it in your csproj.

[JWilh]

Hi,

looks really good 👍 , I like the "are updated to latest version respecting semver."
Would it be possible to add some sort of "--lastestCompatibleVersion" parameter,
cause from time to time you just want everything to be up to date and then if the build/unit tests are failing,
you switch to a more "manual" approach, where each package is checked individually?
(but of cause ignoring .net 5.0 only packages if the current project is still on .net core 3.1 for example)

Would it be possible to specify a package name filter with "wildcards" for example like "MyVendor.*",
so internal packages can also be updated respecting update orders without combability check issues during the update
without updating external packages?
(so no batch is needed with manually calling the update for the packages in the "dependency order" of the packages)

thanks a lot

[nkolev92]

Shouldn't this be handled by a "Do you want to continue [y/n]" check? Linux package managers do this.

The dotnet commands are non interactive by default, so blocking for input might not be an option right now.

[dasMulli]

The dotnet commands are non interactive by default

Plus a large set of projects will be in source control (I'd wish for dotnet new templates to initialize a git repo as well just like ng new does for angular if the target dir is not already in VCS), whereas you usually can't git reset --hard your whole linux system (not that I wouldn't have needed it in the past 🤣).

[BlackGad]

@JonDouglas any progress? Seems #5208 this issue also related to this.

1. Why do you use single source but not the nuget.config?
2. What about solution level update?
3. Will there be wildcards?

[Craige]

What is going on with this?

[nnamdiogbu]

Hi @JonDouglas, Any updates on this topic?

[JonDouglas]

Sorry, this has not been on my near-term list. I am hopeful to return to this next year. I apologize for not providing an update sooner as I was off on paternity leave and now focusing on some other large features. When this has our attention again, I will post a full spec on https://github.com/NuGet/Home/pulls & ask for everyone here to provide feedback.

I will also incorporate the various comments since my last post when working on that artifact. Thanks all!

[eddex]

[SimonCropp]

here is my hacked approach https://github.com/SimonCropp/PackageUpdate

[OskarKlintrot]

And here's my approach: https://github.com/OskarKlintrot/UpdatR. I tried to make it's output pr- and ci/cd-friendly, similar to nukeeper.

[Balkoth]

I would love to see this feature finally making into dotnet.

[OskarKlintrot]

Me too, I really hope they also make it stick to supported versions only! That is very useful to have!

[divinebovine]

If it helps anyone, I just wrote a bash script to update everything to the latest stable. It searches the current directory for all C# projects and updates all outdated packages. I'm sure it could be improved but it works.

for PROJECT in $(find . -iname '*.csproj')
do
  for PACKAGE in $(dotnet list $PROJECT package --outdated | grep '>' | sed -r 's/^ *> ([a-zA-Z0-9\.]*) .*$/\1/gm')
  do
    dotnet add $PROJECT package $PACKAGE
  done
done
echo Update Complete

Here is a vscode task that can be added as a user level task.

{
    "label": "Update Nuget Dependencies",
    "type": "shell",
    "command": "for PROJECT in $(find . -iname '*.csproj'); do for PACKAGE in $(dotnet list $PROJECT package --outdated | grep '>' | sed -r 's/^ *> ([a-zA-Z0-9\\.]*) .*$/\\1/gm'); do dotnet add $PROJECT package $PACKAGE; done; done; echo Update Complete",
    "presentation": {
        "echo": true,
        "reveal": "always",
        "focus": false,
        "panel": "shared",
        "showReuseMessage": true,
        "clear": false
    },
    "problemMatcher": []
}

[JonDouglas]

Hi friends,

I have published a draft proposal for this feature. Please feel free to comment and provide your feedback on it.

#11812

I tried my best to incorporate all the feedback here while also comparing to other ecosystems and existing feedback we've heard over the last year or so.

[RivenSkaye]

I'm not sure if this is the right place for this, but on a system with grep, you can implement this with:

dotnet list package --outdated | grep -o '> \S*' | grep '[^> ]*' -o | xargs -L 1 dotnet add package

This uses dotnet list package --outdated to get a list of packages to update, some grep commands that I should be embarassed about writing to extract the package names, and then dotnet add package to do the actual update.

@brendanlong @AlirezaHaghshenas you can even chop out a grep call if you have GNU Grep (or another grep that provides PCRE expressions) using dotnet list packages --outdated | grep -oP "\>\s+\K\S+" | xargs -L 1 dotnet add package
grep -o: only keep matching components
grep -P: PCRE to allow for special options
\>\s+: match the starting segment
\K: keep matches after this point, which prevents the second grep from being required to chop off the > prefix
\S+: all uninterrupted non-whitespace characters, prevents empty lines and should be a tad more robust against formatting differences

Might just toss a utility script somewhere on my path to combine this with @divinebovine's outer loop logic

[MMeshkiny]

dotnet list package --outdated | grep -o '> \S.' | grep '[^> ].' -o | awk '{system("dotnet add package "$1 " -v " $4)}'

[marshallr12]

So about 8 years later, there's still no dotnet update command?

[NCLnclNCL]

hahâ

[reinux]

dotnet list package --outdated | grep -o '> \S.' | grep '[^> ].' -o | awk '{system("dotnet add package "$1 " -v " $4)}'

@MMeshkiny Just for the benefit of anyone else looking for solutions, could you specify which environment/shell this is for? @RivenSkaye 's command worked in fish shell, but this one didn't.

[RivenSkaye]

Both should work in any env providing the GNU utilities (there is also a GNU awk), though both just use pretty standard POSIX-y tooling. Try and see if your package manager provides an awk package