Versioning.NET
A dotnet tool that automatically increments versions in csproj files based on git commit hints. (by cbcrouse)
Nerdbank.GitVersioning
Stamp your assemblies, packages and more with a unique version generated from a single, simple version.json file and include git commit IDs for non-official builds. (by dotnet)
Our great sponsors
| Versioning.NET | Nerdbank.GitVersioning | |
|---|---|---|
| 3 | 7 | |
| 19 | 1,294 | |
| - | 2.0% | |
| 3.6 | 8.5 | |
| 12 months ago | 10 days ago | |
| C# | C# | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Versioning.NET
Posts with mentions or reviews of Versioning.NET.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-24.
-
Make Your .NET Startup Code More Modular with StartupOrchestration.NET
Plus, if you're looking for a way to automate versioning in your .NET projects, check out my Versioning.NET repository, which is also used to version StartupOrchestration.NET.
- Question about app versioning...
- Automatic .NET Versioning Tool
Nerdbank.GitVersioning
Posts with mentions or reviews of Nerdbank.GitVersioning.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-01.
-
How to set up automatic versioning
i have been using Nerdbank GitVersioing https://github.com/dotnet/Nerdbank.GitVersioning
-
Question on detection multiple path changes
The https://github.com/Azure/ResourceModules repo (which I recommend strongly, if you are just starting with template specs/bicep modules) seems to be at least referencing https://github.com/dotnet/Nerdbank.GitVersioning though when I peeked at their pipelines I'm not sure if they are actually utilizing it for version numbers. For me it was a bit too complex approach, but might suit you.
-
CI/CD for .net 6, using GitHub actions
So, is there a complexity with delivering a NuGet package? Yes. NuGet package versioning can be a big undertaking when it comes to manual deployments, much less CD; as there is a requirement of NuGet packages being immutable. Does this mean that for every check in, on every potential branch that will be pushed to NuGet, you need to update some text file or code to indicate the next built version? That was my initial thinking, but thankfully that is not the case with the help of Nerdbank.GitVersioning.
-
Automatic .NET Versioning Tool
I would suggest you compare with the readme on https://github.com/dotnet/Nerdbank.GitVersioning (FD: this is what I use for versioning my projects, so I'm already very familiar with it), which has most of the details up front (i.e. I don't have to go browsing through multiple wiki pages). It clearly calls out: - What does the package accomplish? (it adds semver information based on git history) - What is it compatible with? ("[dotnet] assemblies, VSIX, NuGet, NPM, and more") - What sets it apart? (#1: every commit generates a unique version, and builds reproducibility is prioritized. #2-4: everything is automatic.) - Further down it talks about how it calculates versions, and how to calculate between versions and git commits (i.e. how does the automatic part work)
-
What is the “standard” method of versioning your applications?
GitVersioning. Auto-increments based on commit. Integrates into your build and automatically adds AssemblyInfo. https://github.com/dotnet/Nerdbank.GitVersioning
- Best practices for versioning in Release Pipelines
-
Run EF Core Queries on SQL Server From Blazor WebAssembly
How to adopt a versioning strategy using tools like Nerdbank GitVersion
What are some alternatives?
When comparing Versioning.NET and Nerdbank.GitVersioning you can also consider the following projects:
Evolve - Database migration tool for .NET and .NET Core projects. Inspired by Flyway.
minver - 🏷 Minimalistic versioning using Git tags.
dotnet-setversion - .NET Core CLI tool to update the version information in .NET Core *.csproj files
AspNetCore.Docs - Documentation for ASP.NET Core
GitVersion - From git log to SemVer in no time
Verlite - Automatically version projects via semantic git tags with a focus on being lite, optimized for continuous delivery.
marionette - Marionette is a test automation framework based on image and text recognition for .NET.
liz - liz (ˈlɪz) is a tool to extract license-information from your project/solution aimed on a fast and correct process. Whether it's via a dotnet-CLI-Tool, Cake-Addin or Nuke-Addon
ExpressionPowerTools - Power tools for working with IQueryable and Expression trees.
NuKeeper - Automagically update nuget packages in .NET projects
CommandLineUtils - Command line parsing and utilities for .NET
Versioning.NET vs Evolve
Nerdbank.GitVersioning vs minver
Versioning.NET vs dotnet-setversion
Nerdbank.GitVersioning vs AspNetCore.Docs
Versioning.NET vs GitVersion
Nerdbank.GitVersioning vs Verlite
Versioning.NET vs marionette
Nerdbank.GitVersioning vs dotnet-setversion
Versioning.NET vs liz
Nerdbank.GitVersioning vs ExpressionPowerTools
Versioning.NET vs NuKeeper
Nerdbank.GitVersioning vs CommandLineUtils