MagicCSharp.App 1.0.0

.NET 9.0 This package targets .NET 9.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package MagicCSharp.App --version 1.0.0
                    


                    

                
NuGet\Install-Package MagicCSharp.App -Version 1.0.0
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="MagicCSharp.App" Version="1.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="MagicCSharp.App" Version="1.0.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="MagicCSharp.App" />
                    


                            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 MagicCSharp.App --version 1.0.0
                    


                    

                
#r "nuget: MagicCSharp.App, 1.0.0"
#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 MagicCSharp.App@1.0.0
#: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=MagicCSharp.App&version=1.0.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=MagicCSharp.App&version=1.0.0
                    


                            Install as a Cake Tool

MagicCSharp.App

Everything a MagicCSharp web service needs, in two calls.

var builder = WebApplication.CreateBuilder(args);
builder.AddMagicApp();

var app = builder.Build();
app.UseMagicApp(builder);
app.Run();

That registers use cases and their dependencies, IClock, Snowflake IDs, request-ID tracking, in-process events, single-machine scheduling defaults, problem-details error handling and controllers — then builds the pipeline in the order those need, and resolves every registration once at startup so a miswired dependency fails the deploy rather than the first request.

What it brings in

MagicCSharp, MagicCSharp.AspNetCore, MagicCSharp.Events, MagicCSharp.Scheduling.

This is a shortcut, not a layer. Every call it makes is public on the package that owns it, so outgrowing the defaults means replacing this with the five lines it stands for — not working around it.

Use the individual packages when you want to choose each piece, and for anything that is not a web service: a worker, a console app, a test project. A project that only needs IClock should reference MagicCSharp, not this.

Changing the defaults

builder.AddMagicApp(new MagicAppOptions
{
    Controllers = false,        // minimal APIs
    Scheduling = false,         // more than one instance — register your own store and lock provider
    KeyGeneratorId = 3,         // stable per instance, rather than random
});
Option Default
Events on Handler discovery, plus in-process dispatch unless something already claimed IEventDispatcher
OpenTelemetryMetrics off Event metrics through OpenTelemetry rather than discarded
Scheduling on The single-machine schedule store and file-system lock
LockDirectory temp Where the file lock provider writes
ErrorHandling on Exceptions to RFC 7807 responses
Controllers on AddControllers and MapControllers
Preflight on Resolve every registration at startup
KeyGeneratorId random Snowflake generator id, 0-1023
AssemblyFilter non-framework Which assemblies are scanned for use cases

Pass the same options to both calls.

Kafka or SQS instead of in-process events

Register the transport before AddMagicApp, and it is left alone:

builder.Services.AddMagicKafkaEvents(kafkaConfig);
builder.AddMagicApp();

Same for scheduling: register your own IScheduleStore and IDistributedLockProvider first and the single-machine defaults step aside.

Product Compatible and additional computed target framework versions.
.NET net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in 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
1.0.3 25 10/6/2026
1.0.2 369 9/24/2026
1.0.1 92 9/24/2026
1.0.0 88 9/23/2026