HardenedThe wiring is written during the build

Mark a method with a route or a function name, and a source generator emits the routing table, the parameter binding and the registration code before the assembly is written.

Get started

Project templates

AWS Lambda

View on GitHub

Attributed handlers on the left becoming a generated route table on the right

Handlers, not controllers

A route is an attribute on a method of a plain class. No base class, no IActionResult, no AddControllers(). The generator reads the attribute and emits the handler that calls your method.

Routing

Binding decided at compile time

Path tokens, query strings, headers, the body and injected services each bind through code emitted for that one handler's exact signature. A binding that cannot work is a build error.

Parameter binding

The same application on Lambda

Swap the runtime module and the handlers you already wrote run behind API Gateway, on a DynamoDB stream, or over an SQS batch — with partial batch responses and structured CloudWatch logging wired in.

AWS runtimes

Configuration that names its variables

A configuration model is a partial class of private fields. The generator writes the interface, the implementation and the environment variable reads.

Configuration

Tests that boot the real application

A test method declares the services it wants as parameters and the framework builds the real application around it, substituting mocks where you ask for them.

Testing

A handler and an application

Attribute the method. The routing table, the parameter binding and the registration code are emitted during the build.

csharp

[HardenedModule]
[KestrelRuntime]
public partial class Application;

public class GreetingController {
    [Get("/hello/{name}")]
    public string Hello(string name) => $"Hello, {name}!";
}

csharp

// Program.cs
var services = new ServiceCollection();

services.AddLogging(logging => logging.AddSimpleConsole(options => options.SingleLine = true));
services.AddHardenedEnvironment(args);

new Application().PopulateServiceCollection(services);

await using var app = HardenedKestrelApplication.Create(
    services, kestrel => kestrel.ListenAnyIP(5080));

await app.RunAsync();

Or skip the wiring — dotnet new hardened-web writes all of it, with tests:

bash

dotnet new install Hardened.Templates
dotnet new hardened-web -n Greeter

Set EmitCompilerGeneratedFiles in the project file and the routing table, the handler and the binding code are all under obj/ as ordinary C#.

Two repositories, one framework

The core framework and the AWS integrations version and ship separately, so an application only carries what it uses.

Repository	What it holds
Hardened.Framework	Modules, DI, configuration, routing, binding, templates, testing
Hardened.Amz	Lambda runtimes, DynamoDB and SQS clients, CDK constructs