explaingit

nancyfx/nancy

7,106C#Audience · developerComplexity · 3/5LicenseSetup · moderate

TLDR

Archived C# web framework for building HTTP APIs on .NET that minimized boilerplate so your route code stayed clean, no longer actively maintained, but permissively licensed for forking.

Mindmap

mindmap
  root((nancy))
    What it did
      HTTP API framework
      Minimal boilerplate
      Auto module discovery
    Key features
      Route definitions
      View engines
      Content negotiation
    Hosting options
      ASP.NET
      OWIN
      Self-hosted
    Status
      Archived
      Permissive license
      Migration needed
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Maintain or migrate existing .NET applications that were built with the Nancy framework.

USE CASE 2

Study Nancy's routing and module design as a reference for clean HTTP API architecture patterns in C#.

Tech stack

C#.NETMonoOWIN

Getting it running

Difficulty · moderate Time to first run · 30min

Project is archived with no active development, for new projects migrate to ASP.NET Core Minimal APIs instead.

Use and fork freely for any purpose including commercial, the project name and logos may not be reused.

In plain English

Nancy was a C# web framework for building HTTP-based services on the .NET platform, including .NET Framework.NET Core, and Mono. The project is no longer actively maintained, and the repository now leads with that announcement. Former team members are available for paid support or migration help if your organization still depends on it in production. The central philosophy was what the project called the "super-duper-happy-path": a framework designed to just work without pushing configuration or ceremony onto the developer. New modules were automatically discovered when added. Dependencies were wired up without manual registration. Core behaviors like routing strategy or dependency container could be swapped with minimal effort. The idea was for Nancy's own code to stay invisible so your application code could be the focus. In practice, Nancy handled all standard HTTP request types and provided a short, readable syntax for defining routes and returning responses. You could return a plain string, a status code, or a stream directly from a route handler without wrapping it in a special object. The framework included support for several view and template engines such as Razor and Spark, advanced route pattern matching, content negotiation, and a testing framework for verifying your application's behavior. Nancy ran on multiple hosting environments including ASP.NET, WCF, self-hosting, and OWIN-compatible hosts, so it was not tied to a single deployment setup. It attracted more than 150 contributors and around 7,100 GitHub stars during its active life. If you are evaluating it for a new project, bear in mind it is archived software with no active development. The permissive license allows forking for maintenance if needed, though the project name and logos are not available for reuse.

Copy-paste prompts

Prompt 1
I have an existing Nancy application on .NET Framework. How do I migrate its routes and modules to ASP.NET Core Minimal APIs?
Prompt 2
Show me the Nancy syntax for a GET route that returns JSON, and show the equivalent in modern ASP.NET Core.
Prompt 3
My Nancy app uses a custom dependency injection container. How do I replicate that pattern in ASP.NET Core's built-in DI?
Prompt 4
I'm running Nancy on OWIN and need to upgrade. What is the migration path to ASP.NET Core middleware?
Open on GitHub → Explain another repo

← nancyfx on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.