Skip to main content

How to set the package version when using dotnet pack

With the dotnet pack command you can build a project and create a Nuget package.

By default, when you execute this command the package version will be set to 1.0.0. If you want to specify the package version you can either set the Version or the PackageVersion in your csproj file:

If you are using the Version parameter both the FileVersion of the embedded dll and the NuGet package version will be updated. Using the PackageVersion will only impact the version number of the NuGet package. By default, PackageVersion takes the same value as Version.

You can override the package version at pack time by using the PackageVersion parameter :

dotnet pack /p:PackageVersion=1.2.3-beta

It is also possible to set a VersionPrefix and VersionSuffix. The VersionPrefix allows you to set a “base” version number. This can be combined with a VersionSuffix to create the final version.

For example, when you set the VersionPrefix to 1.2.3 and VersionSuffix to beta, the Version will be set to 1.2.3-beta.

You can control the VersionSuffix at pack time using the --version-suffix parameter:

dotnet pack --version-suffix beta

Remark: If you have set the PackageVersion using the --version-suffix will have no effect.

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