Generate a new OWIN Startup.cs by picking middleware (CORS, static files, cookie/OAuth authentication, Web API, SignalR, session, error page); or paste an existing OWIN Configuration(IAppBuilder app) method and migrate it to a .NET 6+ minimal-hosting Program.cs with a per-line breakdown of what changed. Includes a standalone OWIN → ASP.NET Core middleware reference table.
app.Use<TypeName>(); — leave blank to skip.Check the middleware you need — the code regenerates live. Order follows common OWIN convention (CORS/static files first, auth next, then Web API/SignalR); see inline comments for anything left ambiguous.
Generate a new OWIN Startup.cs by picking middleware (CORS, static files, cookie/OAuth authentication, Web API, SignalR, session, error page); or paste an existing OWIN Configuration(IAppBuilder app) method and migrate it to a .NET 6+ minimal-hosting Program.cs with a per-line breakdown of what changed. Includes a standalone OWIN → ASP.NET Core middleware reference table.
Paste your Configuration(IAppBuilder app) method into the Migrate tab. The tool produces a .NET 6+ minimal-hosting Program.cs with a per-line breakdown of what changed; some items, such as authentication settings, still need manual porting.
The Middleware Reference tab is a lookup table mapping OWIN calls to their ASP.NET Core counterparts.
Yes, the Startup Generator lets you pick middleware such as CORS, static files, cookie or OAuth bearer authentication, Web API, SignalR, session and error page.
Yes, the OData Query Builder tab builds $filter, $orderby, $top, $skip, $select, $expand and $count options into a query string and can run it against sample JSON.
No. This tool runs entirely in your browser — your input is processed locally on your device and is never uploaded or stored on a server.