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:

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should

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.