Breaking down monolothic systems into smaller components that are maintained by specific people in separate git repositories and distributed as NuGet packages is becoming the standard these days. But what if your component needs to expose some kind of HTTP end-point such as a WebAPI controller or an embedded management website? How do you host such a component in another system without affecting it's hosting model? This is were the Open Web Interface for .NET comes to the rescue. Even the next version of ASP.NET is completely based on OWIN hosting. In this session I'm going to explain you how to build OWIN middleware components and how to host these in an IIS website, a Windows Service or even in a command-line tool.
Dennis is an experienced .NET architect with a broad interest in Application Lifecycle Management, SOA, OO and Design Patterns. He is specialized in designing enterprise solutions based on the .NET technologies as well as providing coaching on all aspects of designing, building and maintaining enterprise systems.
He is the author of www.fluentassertions.com, an assertion framework for fluently asserting the outcome of unit tests and he has publishing coding guidelines for C# 3.0, C# 4.0 and C# 5.0 on www.csharpcodingguidelines.com since 2001. He also maintains a blog on his everlasting quest for better solutions at www.continuousimprover.com. You can reach him on twitter through @ddoomen.