Carter 8.2.1

dotnet add package Carter --version 8.2.1                
NuGet\Install-Package Carter -Version 8.2.1                
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="Carter" Version="8.2.1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Carter --version 8.2.1                
#r "nuget: Carter, 8.2.1"                
#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.
// Install Carter as a Cake Addin
#addin nuget:?package=Carter&version=8.2.1

// Install Carter as a Cake Tool
#tool nuget:?package=Carter&version=8.2.1                


Carter is a framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing the code to be more explicit and most importantly more enjoyable.

For a better understanding, take a good look at the samples inside this repo. The samples demonstrate usages of elegant extensions around common ASP.NET Core types as shown below.

Other extensions include:

  • Validate<T> / ValidateAsync<T> - FluentValidation extensions to validate incoming HTTP requests which is not available with ASP.NET Core Minimal APIs.
  • BindFile/BindFiles/BindFileAndSave/BindFilesAndSave - Allows you to easily get access to a file/files that has been uploaded. Alternatively you can call BindFilesAndSave and this will save it to a path you specify.
  • Routes to use in common ASP.NET Core middleware e.g., app.UseExceptionHandler("/errorhandler");.
  • IResponseNegotiators allow you to define how the response should look on a certain Accept header(content negotiation). Handling JSON is built in the default response but implementing an interface allows the user to choose how they want to represent resources.
  • All interface implementations for Carter components are registered into ASP.NET Core DI automatically. Implement the interface and off you go.


  • Latest NuGet Release NuGet Version
  • Latest NuGet Pre-Release NuGet Version
  • Lateset CI Release
  • Build Status Build Status

Join our Slack Channel

Join our slack channel


Carter uses IEndpointRouteBuilder routing and all the extensions IEndpointConventionBuilder offers also known as Minimal APIs. For example you can define a route with authorization required like so:

app.MapGet("/", () => "There's no place like").RequireAuthorization();

Where does the name "Carter" come from?

I have been a huge fan of, and core contributor to Nancy, the best .NET web framework, for many years, and the name "Nancy" came about due to it being inspired from Sinatra the Ruby web framework. Frank Sinatra had a daughter called Nancy and so that's where it came from.

I was also trying to think of a derivative name, and I had recently listened to the song Empire State of Mind where Jay-Z declares he is the new Sinatra. His real name is Shaun Carter so I took Carter and here we are!

CI Builds

If you'd like to try the latest builds from the master branch add to your NuGet.config and pick up the latest and greatest version of Carter.

Getting Started

You can get started using either the template or by adding the package manually to a new or existing application.


  1. Install the template - dotnet new install CarterTemplate

  2. Create a new application using template - dotnet new carter -n MyCarterApp -o MyCarterApp

  3. Go into the new directory created for the application cd MyCarterApp

  4. Run the application - dotnet run


  1. Create a new empty ASP.NET Core application - dotnet new web -n MyCarterApp

  2. Change into the new project location - cd ./MyCarterApp

  3. Add Carter package - dotnet add package carter

  4. Modify your Program.cs to use Carter

var builder = WebApplication.CreateBuilder(args);

var app = builder.Build();

  1. Create a new Module
    public class HomeModule : ICarterModule
        public void AddRoutes(IEndpointRouteBuilder app)
            app.MapGet("/", () => "Hello from Carter!");
  1. Run the application - dotnet run


var builder = WebApplication.CreateBuilder(args);
builder.Services.AddSingleton<IActorProvider, ActorProvider>();

var app = builder.Build();


public class HomeModule : ICarterModule
    public void AddRoutes(IEndpointRouteBuilder app)
        app.MapGet("/", () => "Hello from Carter!");
        app.MapGet("/qs", (HttpRequest req) =>
            var ids = req.Query.AsMultiple<int>("ids");
            return $"It's {string.Join(",", ids)}";
        app.MapGet("/conneg", (HttpResponse res) => res.Negotiate(new { Name = "Dave" }));
        app.MapPost("/validation", HandlePost);

    private IResult HandlePost(HttpContext ctx, Person person, IDatabase database)
        var result = ctx.Request.Validate(person);

        if (!result.IsValid)
            return Results.UnprocessableEntity(result.GetFormattedErrors());

        var id = database.StorePerson(person);

        ctx.Response.Headers.Location = $"/{id}";
        return Results.StatusCode(201);

public record Person(string Name);

public interface IDatabase
    int StorePerson(Person person);

public class Database : IDatabase
    public int StorePerson(Person person)
        //db stuff

More samples


As mentioned earlier Carter will scan for implementations in your app and register them for DI. However, if you want a more controlled app, Carter comes with a CarterConfigurator that allows you to register modules, validators and response negotiators manually.

Carter will use a response negotiator based on System.Text.Json, though it provides for custom implementations via the IResponseNegotiator interface. To use your own implementation of IResponseNegotiator (say, CustomResponseNegotiator), add the following line to the initial Carter configuration, in this case as part of Program.cs:

    builder.Services.AddCarter(configurator: c =>

Here again, Carter already ships with a response negotiator using Newtonsoft.Json, so you can wire up the Newtonsoft implementation with the following line:

    builder.Services.AddCarter(configurator: c =>
Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (12)

Showing the top 5 NuGet packages that depend on Carter:

Package Downloads

Package Description


Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.


A library to extend Carter to handle the siren hypermedia media type.


Api crosscutting concerns


A Clean Architecture Base Template comprising all Baseic and Abstract and Contract types for initiating and structuring a .Net project.

GitHub repositories (10)

Showing the top 5 popular GitHub repositories that depend on Carter:

Repository Stars
Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
An implementation of HTTP Caching in .NET Core and 4.5.2+ for both the client and the server
A lightweight low ceremony API for web services.
SOA Done Right
This repository contains the implementation of domain-driven design and clear architecture in ASP.NET Core.
Version Downloads Last updated
8.2.1 13,777 6/6/2024
8.2.0 8,538 5/24/2024
8.1.0 18,853 5/11/2024
8.0.0 153,621 12/4/2023
7.2.0 60,437 9/21/2023
7.1.0 102,291 4/22/2023
7.0.1 13,585 3/15/2023
7.0.0 30,903 11/21/2022
7.0.0-beta 149 11/21/2022
7.0.0-alpha1 124 11/18/2022
6.1.1 113,908 7/20/2022
6.1.0 2,402 7/15/2022
6.0.0 113,716 11/22/2021
6.0.0-rc4 1,120 11/12/2021
6.0.0-rc3 426 11/2/2021
6.0.0-rc2 326 10/25/2021
6.0.0-pre2 1,553 8/13/2021
5.2.0 138,696 9/6/2020
5.1.0 62,634 1/27/2020
5.0.0 4,515 11/25/2019
4.2.0 22,442 5/28/2019
4.1.0 5,886 3/6/2019
4.0.0 1,880 3/5/2019
3.11.0 5,452 12/31/2018
3.10.0 4,719 12/31/2018
3.8.0 5,457 10/17/2018
3.7.0 12,370 5/31/2018
3.6.0 4,847 4/12/2018
3.5.0 2,482 4/7/2018