Maintain or migrate existing .NET applications that were built with the Nancy framework.
Study Nancy's routing and module design as a reference for clean HTTP API architecture patterns in C#.
| nancyfx/nancy | dotnetcore/cap | dotnet/reactive | |
|---|---|---|---|
| Stars | 7,106 | 7,084 | 7,146 |
| Language | C# | C# | C# |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 3/5 | 3/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Project is archived with no active development, for new projects migrate to ASP.NET Core Minimal APIs instead.
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.
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.
Mainly C#. The stack also includes C#, .NET, Mono.
Use and fork freely for any purpose including commercial, the project name and logos may not be reused.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.