Skip to main content

NuGet Central Package Management

The way that your NuGet package dependencies are managed changed over the years. Originally, the list of NuGet packages used by a project where managed inside a packages.config file.

More recently, the concept of a <PackageReference /> got introduced that allowed you to manage your NuGet dependencies directly within your project file.

Both approaches manage dependencies at the project level. This is not ideal for multi-project solutions as every project can use different versions of the same dependency. Visual Studio can help you to consolidate package versions but it remains cumbersome when your solutions start to grow.

Starting with NuGet 6.2, you can centrally manage your dependency versions in your projects with the introduction of a Directory.Packages.props file.

Getting started

To get started with central package management, create a Directory.Packages.props file at the root of your solution.

Remark: It is possible to use multiple Directory.Packages.props files in different locations. In that case the props file closest to your project will be evaluated.

Inside this file, you need to specify the package version that should be used inside your solution through the <PackageVersion /> element.

You still need to use the <PackageReference /> in your project files, but without a Version attribute to infer the centrally managed version instead.

To use NuGet Central Package management you need at least:

More information: https://devblogs.microsoft.com/nuget/introducing-central-package-management/

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