CQRSharp.Generators 2.2.4

There is a newer version of this package available.
See the version list below for details. 
dotnet add package CQRSharp.Generators --version 2.2.4
                    


                    

                
NuGet\Install-Package CQRSharp.Generators -Version 2.2.4
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="CQRSharp.Generators" Version="2.2.4" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="CQRSharp.Generators" Version="2.2.4" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="CQRSharp.Generators" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add CQRSharp.Generators --version 2.2.4
                    


                    

                
#r "nuget: CQRSharp.Generators, 2.2.4"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package CQRSharp.Generators@2.2.4
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=CQRSharp.Generators&version=2.2.4
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=CQRSharp.Generators&version=2.2.4
                    


                            Install as a Cake Tool

A set of Roslyn source code generators that allow Native AoT compatibility for the CQRSharp Library.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.2.6 245 4/20/2025
2.2.5 208 4/11/2025
2.2.4 217 4/7/2025
2.2.3.1 214 3/11/2025
2.2.3 221 3/10/2025
2.2.2 266 3/8/2025

🚀 Release Notes for 2.2.4

           🔧 Changes
           - Replaced string-based detection of handlers and requests with a new attribute-driven approach.
           - Improved diagnostic messages (e.g., warnings if a required attribute is missing or if no handlers are found).
           - Added new file CQRSharp.Shared.Attributes.RegistrationMarkers.cs providing HandlerTypeAttribute and RequestMarkerAttribute.
           - Improved the source code generators drastically - complete Native AoT support for all functionality.
           - Complete elimination of reflection in the codebase contributing to AoT support and better performance on runtime.
           - All registries that are responsible for mapping out various ConccurentDictionary instances on compile-time now share a very recognizable, and simple pattern, involving IDataRegistrar, Registrar and their respective interfaces and implementations. The code now utilizes ModuleInitializer to run code that binds the Registrar instances to the generated code on runtime.
           - Modified all source generator code that involves itself with registering various classes with the DI container to use a unified registrar system. This ensures minimal hard-coding.
           - The library now has complete support for custom context types implementations in IRequestContextFactory - earlier, this was locked to a single context type, forcing users to write their own workarounds for creation of context instances.

           📂 Breaking Changes?
           - The CQRSharp.Kafka project has been fully removed. No built-in Kafka publishing or consumer services remain.
           - Minor API shift in RateLimiter tests and usage from RateLimitedContext to IRateLimitedContext. Now all contexts that want to utilize the rate limiter will need to inherit from the IRateLimitedContext, to implement the required parameters for the rate limiter to execute its logic.