Recently I’ve run into an ASP.NET Core MVC bug when an HTTP request with multipart content-type and empty body would cause an unhanded IOException exception to be thrown in MVC framework. However, when sending an invalid request I’d expect to receive a 400 error response code.
In my previous blog post I’ve implemented a very simple application to illustrate dependency injection (DI) using Ninject. While Ninject is flexible and powerful, you might want to try different dependency injection libraries before you make your final decision on what to use. And this time I wanted to look into the latest dependency injection library which comes as a default option for MVC 6 and .NET Core – Microsoft Dependency Injection. And yes, the name is very easy to remember :)
It has been a while since my last blog post, and I decided to continue series of simple examples of dependency injection (DI). Last time I had an example of not so well known but extremely simple and fast Simple Injector. This time I wanted to replace the Simple Injector with a more popular Ninject, and see if there are any big differences in terms of set up. I chose Ninject mostly just because of the Japan-related name:)
A very quick tip how to solve “HTTP Error 403.16 – Forbidden” issue when trying to run a new MVC web application on Windows 10 using IIS 10 Express. After some quick tests and research on Google I made a conclusion that this problem is actually not related neither to Windows, nor IIS.
Using ASP .NET MVC 5 still has the classical web application project structure (compared against the new MVC 6), and dependency injection (DI) is quite straightforward using a third party library. And to make this process even simpler, I decided to try out Simple Injector. It’s a very simple and fast DI .NET library.