Generating clients for your APIs with AutoRest

When building Web APIs it's often required to provide client adapters between various programming stacks and raw HTTP REST APIs. These 'clients' can be built manually but it's often a rather tedious task and it adds to your development efforts as you need to keep the clients in sync with... »

Bring your own DI container to ASP.NET 5 - Unity

Now that we understand some basics of how dependency injection is handled by ASP.NET 5 we are ready to start rolling out our integration components for our container of choice. The process may not that straightforward at times and different containers have their quirks. I believe things will improve when new bits actually go GA and it's likely that containers »

Bring your own DI container to ASP.NET 5

As you probably know ASP.NET 5 uses dependency injection from the ground up. It's unlike previous releases where higher level frameworks such as MVC, WebAPI or SignalR provided their own extension points to hook your DI container of choice in. In the new release dependency injection is going to be used throughout the stack from infrastructure and middleware to higher »

Getting to know the new ASP.NET 5 configuration framework

.NET applications traditionally relied on `System.Configuration` components for accessing and managing configurations from the machine wide settings down to application and user settings. The new release of .NET revisits the configuration story by bringing on a brand new configuration framework... »

Understanding ASP.NET 5 middleware

Principals and design approaches that we have seen in OWIN specification and some of its implementations (for Microsoft servers and frameworks the most notable is Katana) found their way into ASP.NET 5. In this post I want to focus on one of the core concepts which is middleware. »