The Acumen ASP.NET MVC development team started working with the new Web API 2 controllers released with Visual Studio 2013, and quickly hit some important issues that took some research to resolve. Routing and AttributeRouting and using Web API 2 controllers inside an Area
I helped design an interesting deployment strategy for an Azure application. For one of our projects, we have an existing upgrade solution that will distribute new versions of our ASP.NET application to our clients. One of our clients runs in the app in Azure. To support this automated distributi
Unit testing in .NET is pretty nice when your dependency injection/IoC is set up well, but Entity Framework 6 isn’t the nicest framework for mocking and testing. If you’re using ASP.NET MVC 5, you may have run into this scenario. Problem: You want to use or mock
Me: Kernel.Bind<IDataCache>().To<InMemoryDataCache>().InSingletonScope(); Ninject: Haha, nah. Here’s a new object bro. I don’t know why exactly this happens but for some reason, I’ve seen it happen in more than one project. Binding an implemen
Ninject has some fun quirks. For instance, one "bug" I came across was that if you hit an ASP.NET controller with a custom attribute, the attribute’s constructor-injected dependencies would be null on startup. For example, take the following ActionFilterAttribute: <pre class="language-
Let's say you are doing some work on your AuthConfig class, in your Global.asax, or maybe a static class. You can’t property-inject, and generally, it’s a pain to get this to work. However, if you’re using Ninject for ASP.NET MVC, you can use the following
ASP.NET Web API is a fantastic piece of the .NET family (there is certainly some weirdness since we now have MVC and Web API with nearly identical methods, but ASP.NET MVC 6 is coming :)). However, getting a SPA or mobile hybrid (Ionic!) app working isn’t the most pleasant experience.