Skip to main content

.NET Core - View outdated packages

When creating and maintaining (.NET Core) applications, it is always a good idea to keep the dependencies up-to-date. This helps to fix identified vulnerabilities but also keeps the upgrade path short as you closely stay to the latest package version. In this post I show you 3 ways to identify outdated packages and update them when necessary.

Through the Visual Studio Package Manager

When using Visual Studio, it is easy to find out whether newer versions of the NuGet packages used by your project is available, by using the NuGet Package Manager:

  • Open your solution/project in Visual Studio
  • Go to Tools-> NuGet Package Manager –> Manage NuGet Packages for Solution…
  • Go to the Updates tab, check the Select all packages checkbox and click on Update

Through the dotnet-outdated global tool

A second option is to use the open source global .NET tool: dotnet-outdated.

  • First install the tool using the following command:
dotnet tool install --global dotnet-outdated-tool
  • Now you can call the tool using the following command:
dotnet-outdated
  • To update the  outdated packages run this command:
dotnet-outdated --upgrade

Through the .NET Core CLI

A last option is to use the .NET Core CLI directly.

  • To get the list of outdated packages, run the following command:
dotnet list package --outdated
  • Now if we want to update an outdated package, you can do the following:
dotnet add package PACKAGENAME

Remark: We have to repeat this command for every package that requires an update.

More information

dotnet list package command - .NET CLI | Microsoft Learn

GitHub - dotnet-outdated/dotnet-outdated: A .NET Core global tool to display and update outdated NuGet packages in a project

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more