It seems ironic that up until pretty recently, adding OWIN—an open source standard of decoupling server and application code—wasn’t all that easy to do inside the same open source concept of .NET Core. Mostly it appears we had to rely on Kestrel do the serving, particularly whenever we would create a .NET Core web application from the CLI. What I’m going to present for your inspection today is how easy it is to convert a .NET Core application that is pointing to the full .NET Framework to utilize OWIN to remove the application/server dependencies from one another without major breakage. Or… er, well, ahem… at least to minimize the heartache and cursing.
Something I discovered early about .NET Core was how easy it was to get started. This is due in no small part to the
dotnet command line interface. In its earliest releases, .NET Core utilized the
dnx that felt pretty clunky to use, in my opinion. Then the Microsoft team released the
dotnet command line changes to the toolchain and that transition made working with the CLI feel much smoother.
Greetings, Nerd dizzles! I’ve programmed in a lot of languages over the nearly two decades I’ve been in the software engineering field. Better than half that time I’ve spent in various framework iterations of ASP.NET, C#, and SQL Server. Most of what I’ve done has been “old school.” In other words, building n-tier applications using object-oriented programming and ADO.NET. I’ve been doing that for so long, I guess I’ve become somewhat of a curmudgeon about it, at least if you compare what me to these young, new hotshot developers just coming out of school and building their own startups.