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 }}
Repository navigation
support for bulk-updating references into csproj from commandline(s) - dotnet package update #4103
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.
Reacted by James Griffin, dcumin39, Yehor Hromadskyi, Refael Peres, AraHaan, Dave Bagtas, Yufei Huang, WhatFreshHellIsThis, Adrian Ehrsam, Matisse Hack and 3 more
I would just use the same names as well... dotnet upgradedotnet upgrade-interactive or possibly dotnet package upgradedotnet package upgrade-interactive
Reacted by Chris Paton, Bas Bossink, mudrz, John Reilly, chriscanossi, Fernando Minoru Baba, Craige Leeder, mlhpdx, AraHaan and Austin
changed the title [-]support for bulk-updating references into csproj from commandline(s) - dotnet update package[/-][+]support for bulk-updating references into csproj from commandline(s) - dotnet package update[/+]on Jun 26, 2025
The .NET 10.0.100 SDK had the first version of dotnet package update, which only supports updating one package at a time.
The .NET 10.0.200 SDK will support updating all projects in a solution.
There will always be more polish that can be added. I already opened a few issues for improvements to dotnet package update. Please add 👍 reactions to them to upvote them, or file new issues if none already exist.
Reacted by Marshall Rosenstein, Frulfump, Florian Bruder, Nikolche Kolev and Fernando Alex Helwanger
Reacted by Nikolche Kolev and Fernando Alex Helwanger
Activity
rrelyea commentedon Dec 13, 2016
since add will support "update", we'll prioritize this task as the lowest of the 4:
dasMulli commentedon Dec 19, 2016
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 --allto begin with when updating a project.kjbetz commentedon Nov 14, 2017
I would highly suggest checking out how yarn has taken care of this with
yarn upgradeandyarn upgrade-interactivehttps://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 upgradedotnet upgrade-interactiveor possiblydotnet package upgradedotnet package upgrade-interactiverrelyea commentedon Nov 21, 2017
Notice that #6193 added the additional requests to support cross-project updates, etc...
108 remaining items
[-]support for bulk-updating references into csproj from commandline(s) - dotnet update package[/-][+]support for bulk-updating references into csproj from commandline(s) - dotnet package update[/+]zivkan commentedon Dec 31, 2025
I'm closing this issue as complete.
The .NET 10.0.100 SDK had the first version of
dotnet package update, which only supports updating one package at a time.The .NET 10.0.200 SDK will support updating all projects in a solution.
There will always be more polish that can be added. I already opened a few issues for improvements to dotnet package update. Please add 👍 reactions to them to upvote them, or file new issues if none already exist.