Back to browse
GitHub Repository

An opinionated, embeddable, C# web microframework

8 starsC#

A .NET Web Framework on the Base .NET Core SDK

by utf_8x·Mar 4, 2026·2 points·0 comments

AI Analysis

MidBold Bet

Embeddable .NET web framework sidestepping ASP.NET bloat, but alpha and underspecified.

Strengths
  • True base-.NET-SDK isolation prevents accidental dependencies on Web SDK and reduces scope creep
  • Fluid templating (Liquid-compatible) offers familiar alternative to Razor without XML noise
  • Minimal-by-design ethos appeals to developers tired of ASP.NET's convention-over-configuration baggage
Weaknesses
  • Very early alpha with minimal examples: unclear if routing, middleware, or error handling match ASP.NET maturity
  • Niche win: only solves pain for developers embedding HTTP in non-web .NET apps; broader .NET web dev will stick with ASP.NET
Target Audience

.NET developers embedding HTTP services in existing applications or avoiding ASP.NET Core's scope pollution

Similar To

ASP.NET Core · Sinatra (Ruby) · Express.js (Node.js)

Post Description

I’ve been experimenting with building a web framework directly on top of the base .NET runtime without using the ASP.NET Web SDK.

I'm calling it Wisp.

The main motivation was frustration with some aspects of ASP.NET, especially the requirement to target the Web SDK instead of the base .NET SDK. That makes embedding small HTTP apps inside existing applications harder than it should be since it forces you to pollute your scope with the Web SDK.

I also don't like CSHTML/Razor and wanted a more traditional templating language.

Wisp is a relatively lightweight MVC framework built without any dependencies on the .NET Web SDK.

Some highlights:

- Runs on the base .NET SDK (no ASP.NET dependency) - Traditional MVC controllers - Dependency injection via Microsoft.Extensions.DependencyInjection - Configuration via Microsoft.Extensions.Configuration - Templating via the Fluid engine (Liquid-compatible)

It's still very alpha and definitely rough around the edges, but I've already built a few small applications with it and it works surprisingly well.

The code is written by hand, not vibe-coded.

If you're interested in experimenting with alternative approaches to building web apps in .NET, feedback and contributions are very welcome.

Docs: https://wispframework.github.io/Wisp/

Quick start:

dotnet new install Wisp.Framework.Templates dotnet new wisp.mvc dotnet run

A minimal application looks like this:

var hostBuilder = new WispHostBuilder(); hostBuilder.UseStaticFiles();

var appBuilder = hostBuilder.Build(); appBuilder.UseControllers();

var app = appBuilder.Build(); await app.RunAsync();

It should hopefully Just Work(tm) :)

Similar Projects

Developer Tools●●Solid

Free Windows shell extension for quick .NET assembly inspection

Uses MetadataLoadContext to read assembly metadata without executing any code, then surfaces that data via a native C++ ATL/COM shell extension so you can right‑click DLLs/EXEs and see compilation mode, target framework, PE kind and a clickable recursive reference tree. It’s essentially a safety‑first, lightweight alternative to firing up a decompiler when you just need quick dependency and version info — not flashy or novel, but genuinely useful in day‑to‑day Windows/.NET debugging.

Niche GemWizardry
tebjan
213mo ago
Developer Tools●●●Banger

Interactive fluid simulation in Jax using Brinkman penalization

Draw obstacles with your mouse and get gradient-based inverse design without adjoint solvers.

WizardrySolve My ProblemNiche Gem
arriemeijer
201mo ago