In a previous post [http://davidzych.com/2014/06/02/dependency-injection-in-asp-net-vnext/] I explained how to set up and use the built in dependency injection container in ASP.NET vNext. Today we’re going to look at setting up and using the popular Castle Windsor DI container. In order to use
As a programmer, I spend a lot of time in front of a keyboard and naturally I’ve gotten pretty good at typing. Out of curiosity I took a typing test to see how fast I am [http://www.typeonline.co.uk/typingspeed.php?] (surprisingly I haven’t taken one
One of the big headlines of ASP.NET vNext is that dependency injection is built into the framework. It’s a pretty basic implementation of DI, but although it’s very basic I’m sure it will suffice for most applications. I’ll show how to set up and use
ASP.NET vNext was announced a few weeks ago and there are now some great resources available explaining what it is, why it’s here and why it’s a really freaking important change. Github All of ASP.NET vNext is open source and available on Github. The Home project
ASP.NET vNext is the next version of the ASP.NET web framework. The focus this time around is strip out unnecessary bits and make a leaner, meaner, easier-to-use framework. A few of the things done include: * Side by side deployment of .NET – you can deploy all code, dependencies and