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.

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.