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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more