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)

Nerdbank.GitVersioning Alternatives

Similar projects and alternatives to Nerdbank.GitVersioning

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Nerdbank.GitVersioning alternative or higher similarity.

Nerdbank.GitVersioning reviews and mentions

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
    2 projects | /r/dotnet | 1 Feb 2023
    i have been using Nerdbank GitVersioing https://github.com/dotnet/Nerdbank.GitVersioning
  • Question on detection multiple path changes
    3 projects | /r/azuredevops | 30 May 2022
    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
    3 projects | dev.to | 30 Nov 2021
    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
    5 projects | /r/dotnet | 10 Apr 2021
    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?
    1 project | /r/csharp | 22 Jan 2021
    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
    2 projects | /r/azuredevops | 31 Dec 2020
  • Run EF Core Queries on SQL Server From Blazor WebAssembly
    18 projects | dev.to | 21 Sep 2020
    How to adopt a versioning strategy using tools like Nerdbank GitVersion
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 19 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic Nerdbank.GitVersioning repo stats
7
1,294
8.5
11 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com