From the course: Creating, Debugging, and Deploying NuGet Packages in ASP.NET
Join today to access over 24,900 courses taught by industry experts.
Versioning strategies for NuGet packages
From the course: Creating, Debugging, and Deploying NuGet Packages in ASP.NET
Versioning strategies for NuGet packages
- [Instructor] Versioning strategies for NuGet packages are important for keeping software compatible, stable, and clearly communicating updates to developers and users in the .NET ecosystem. Semantic versioning is the most widely used strategy for NuGet packages, and it follows the format major.minor.patch and optionally, pre-release. But how do you know which part of the version number to change? You change the major part when you introduce breaking changes. If your update is not backward compatible, then you increment the major part. So basically you would move from 1.2.3 to 2.0.0. The minor version is updated for new features that are backward compatible. So when you add new functionality without breaking existing ones, then you increase the minor version. So for example, from 1.2.3 to 1.3.0. The patch part is incremented for backward compatible bug fixes. So if you are fixing a bug that doesn't affect the API, you update the patch version. So it go from 1.2.3 to 1.2.4. The…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
Contents
-
-
-
What is a NuGet package?3m 32s
-
(Locked)
Why use NuGet packages?4m
-
(Locked)
Setting up your development environment3m 58s
-
(Locked)
Creating your first NuGet package project5m 11s
-
(Locked)
Versioning strategies for NuGet packages3m 51s
-
(Locked)
Working with NuGet dependencies4m 5s
-
(Locked)
Setting NuGet package metadata6m 4s
-
-
-
-