Re:ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET...
by WorldMaker on Wednesday January 20, 2016 @02:05PM
(#10940471)
Things are getting more confusing today briefly on the road to getting better.
The new `dotnet` CLI is on its way to becoming much like the `go` CLI as a one-stop-shop for a lot of your IDE needs, cross-platform and easily accessible from your favorite command line and/or code editor.
It should be the case soon that you can `yo` up a new web project (or use some other generator tool if you don't like Yeoman) and then `dotnet web` straight into a simple web server.
Also, at its face OWIN is a lot simpler than it seems. It's simply the name of the "middleware protocol" in modern .NET web applications, similar to the Connect versus Express confusion in NodeJS land in that Express uses/provides "Connect-compatible" middleware, ASP.NET uses/provides "OWIN-compatible" middleware. Maybe that helps a little.
The new `dotnet` CLI is on its way to becoming much like the `go` CLI as a one-stop-shop for a lot of your IDE needs, cross-platform and easily accessible from your favorite command line and/or code editor.
It should be the case soon that you can `yo` up a new web project (or use some other generator tool if you don't like Yeoman) and then `dotnet web` straight into a simple web server.
Also, at its face OWIN is a lot simpler than it seems. It's simply the name of the "middleware protocol" in modern .NET web applications, similar to the Connect versus Express confusion in NodeJS land in that Express uses/provides "Connect-compatible" middleware, ASP.NET uses/provides "OWIN-compatible" middleware. Maybe that helps a little.