Orleans
Nerdbank.GitVersioning
Our great sponsors
Orleans | Nerdbank.GitVersioning | |
---|---|---|
35 | 7 | |
9,821 | 1,296 | |
1.0% | 2.4% | |
9.1 | 8.3 | |
7 days ago | 20 days ago | |
C# | C# | |
MIT License | MIT License |
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
-
.NET 8 – .NET Blog
We should chat more about Reminders v2 - I want to learn more about what you'd like it to provide. Can you comment on the issue (https://github.com/dotnet/orleans/issues/7573)? If you'd like to see some of what is in the works, please message me on Discord and we can chat more about it (https://aka.ms/orleans/discord)
- Orleans v7.2.3 Released
-
how to safely share state in multithreading applications
for ADO scripts config, I ran the main, clustering, and persistence scripts but got runtime error lacking some migration sql object (don't remember the exact error message). But after some debug, I had to run this extra migration script which was not mentioned in that ADO config page.
- Orleans – Cloud Native application framework for .NET – Release v7.1.2
- Maximizing Scalability & Speed — Redis Session Management in C#
-
Temporal .NET SDK
I think Orleans is going to introduce something similar that Temporal has on .NET 8 https://github.com/dotnet/orleans/issues/7487
-
Top 10 bugs found in C# projects in 2022
Something tells me that the developers should have cleared batchOperation a bit later. Judging by the fix, the Orleans developers agree with me.
-
Does anyone have any experience with dapr (ala dapr.io)?
Dapr is created for multi language purpose. If you have only .NET Stack there is mature and more faster Microsoft Orleans. Debugging is easy with local silo - just debugging the same process.
-
How to make the fastest .NET Serializer with .NET 7 / C# 11, case of MemoryPack
There are some more perf improvements coming to Orleans serializer, like this 1.6x improvement to message serialization: https://github.com/dotnet/orleans/pull/8185
- What's new in Orleans 7.0
Nerdbank.GitVersioning
-
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?
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.
Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework
minver - 🏷 Minimalistic versioning using Git tags.
Akka.net - Canonical actor model implementation for .NET with local + distributed actors in C# and F#.
AspNetCore.Docs - Documentation for ASP.NET Core
DotNetty - DotNetty project – a port of netty, event-driven asynchronous network application framework
Verlite - Automatically version projects via semantic git tags with a focus on being lite, optimized for continuous delivery.
Microdot Framework - Microdot: An open source .NET microservices framework
dotnet-setversion - .NET Core CLI tool to update the version information in .NET Core *.csproj files
protoactor-dotnet - Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin
ExpressionPowerTools - Power tools for working with IQueryable and Expression trees.