ASP.NET MVC applications
Using Ninject in Windows client applications (WPF and Windows Forms) was not much different from using it in a Console application. We didn't need any certain configuration to set up Ninject in such applications, because in Windows client applications the developer has the control of instantiating UI components (Forms or Windows), and can easily delegate this control to Ninject. In Web applications, however, it is not the same, because the framework is responsible of instantiating the UI. So, we need to somehow tell the framework to delegate that responsibility to Ninject. Fortunately, asking the ASP.NET .MVC framework to do so is easily possible, but it is not the same for Web Forms applications.
Thanks to Ninject's MVC ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access