Orleans VS Nerdbank.GitVersioning

Compare Orleans vs Nerdbank.GitVersioning and see what are their differences.

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
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Orleans Nerdbank.GitVersioning
35 7
9,762 1,280
0.9% 2.0%
9.1 8.5
7 days ago 27 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.

Orleans

Posts with mentions or reviews of Orleans. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-14.

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
    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)
  • 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

What are some alternatives?

When comparing Orleans and Nerdbank.GitVersioning you can also consider the following projects:

ABP - Open Source Web Application Framework for ASP.NET Core. Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET and the ASP.NET Core platforms. Provides the fundamental infrastructure, production-ready startup templates, application modules, UI themes, tooling, guides and documentation.

ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework

Akka.net - Canonical actor model implementation for .NET with local + distributed actors in C# and F#.

DotNetty - DotNetty project – a port of netty, event-driven asynchronous network application framework

Microdot Framework - Microdot: An open source .NET microservices framework

Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.

minver - 🏷 Minimalistic versioning using Git tags.

protoactor-dotnet - Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin

Spring.Net - Spring Framework for .NET

ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

Fusion - Build real-time apps (Blazor included) with less than 1% of extra code responsible for real-time updates. Host 10-1000x faster APIs relying on transparent and nearly 100% consistent caching. We call it DREAM, or Distributed REActive Memoization, and it's here to turn real-time on!

CSLA .NET - A home for your business logic in any .NET application.