AspNetCore.Docs
Nerdbank.GitVersioning
Our great sponsors
AspNetCore.Docs | Nerdbank.GitVersioning | |
---|---|---|
40 | 7 | |
12,358 | 1,296 | |
1.0% | 2.2% | |
9.9 | 8.3 | |
about 3 hours ago | 17 days ago | |
C# | C# | |
Creative Commons Attribution 4.0 | 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.
AspNetCore.Docs
-
DevDocs
Certain parts of Microsoft Learn are permissive, for example the .NET BCL documentation is Creative Commons Attribution: https://github.com/dotnet/dotnet-api-docs as is ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs (a good hint if documentation is permissively licensed and on GitHub is if there's an edit button at the top.)
The C# language specification is unfortunately a bit fuzzier: https://github.com/dotnet/csharplang/discussions/4855
The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard
-
ASP.NET Core Blazor
looks like 8.0 release? https://github.com/dotnet/AspNetCore.Docs/commit/e8ce5761969...
- Combining Blazor WebAssembly and .Net MVC application - part 1
-
Accessing the HttpContext outside the outside the HttpRequest
I am not sure what you mean,but here you can find all the supported ways of accessing the httpcontext in.net core https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/http-context.md maybe this can help you
- When/why do we need to use UseActifileExceptionHandler()?
-
Migration of WebAPI project from .NET Framework 4.7.2 to .NET 6
Whilst EF6.3 had some support (note: designer doesn’t work) in .NET Core 3.1 (sample), I’m not sure if that applies to NET6. You could certainly give it a try.
-
15 Popular Github Repositories for the Modern Developer of 2023
11. ASP.NET
- SSO Between .Net Framework 4.6.1 MVC and .NET 7
- Big sites in Blazor
-
Blazor Hybrid: WPF/WinUi/MAUI?
Also this discussion https://github.com/dotnet/AspNetCore.Docs/issues/26250
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?
Avalonia.FuncUI - Develop cross-plattform GUI Applications using F# and Avalonia!
Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.
shadowsocks-windows - A C# port of shadowsocks
minver - 🏷 Minimalistic versioning using Git tags.
openiddict-core - Flexible and versatile OAuth 2.0/OpenID Connect stack for .NET
Verlite - Automatically version projects via semantic git tags with a focus on being lite, optimized for continuous delivery.
TcNo-Acc-Switcher - A Super-fast account switcher for Steam, Battle.net, Epic Games, Origin, Riot, Ubisoft and many others! [Moved to: https://github.com/TCNOco/TcNo-Acc-Switcher]
dotnet-setversion - .NET Core CLI tool to update the version information in .NET Core *.csproj files
v2rayN - A GUI client for Windows, support Xray core and v2fly core and others
ExpressionPowerTools - Power tools for working with IQueryable and Expression trees.
atldotnet - Fully managed, portable and easy-to-use C# library to read and edit audio data and metadata (tags) from various audio formats, playlists and CUE sheets
CommandLineUtils - Command line parsing and utilities for .NET