Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What is the Best Way to Organize a ASP.Net MVC Solution Using Dependency Injection?

Tags:

People also ask

Can we use dependency injection in ASP.NET MVC?

The Dependency Injection (DI) Design PatternThe Dependency Resolver in ASP.NET MVC can allow you to register your dependency logic somewhere else (e.g. a container or a bag of clubs). The advantages of using Dependency Injection pattern and Inversion of Control are the following: Reduces class coupling.

Which of the following steps can we use to inject services to view in ASP.NET Core?

We can inject the dependency using @inject directive. ASP.NET Core MVC allows us to inject the dependency into the View. This can be useful for populating the UI elements such as dropdown list. However, the best practice says that "all the data rendered by View should come from Controller class".

What is dependency injection in MVC 5?

Dependency injection is a first-class citizen in ASP.NET Core MVC 5. Part of the new . NET 5, ASP.NET Core MVC 5 is the latest version of Microsoft's framework for building web apps and APIs using the model-view-controller design pattern.

Does ASP NET have dependency injection?

ASP.NET Core supports the dependency injection (DI) software design pattern, which is a technique for achieving Inversion of Control (IoC) between classes and their dependencies. For more information specific to dependency injection within MVC controllers, see Dependency injection into controllers in ASP.NET Core.


I am early in development on a new ASP.Net MVC project and I using this project to get into DI. I'm pretty sure that I am going to go with Structure Map, but that isn't what I am asking about. What I am trying to figure out is how best to organize my solution. Do both the unit test project and the model get a configuration file to map their dependencies or is there one class to rule them all?

Also, are there any newbie traps to avoid before I get too far into this?

Many Thanks, All.....

Update I should add that when I say "organize the solution", I'm not referring to the number of files/folders, etc., but rather how to structure the classes that are involved with DI. In particular, how to manage the bootstrapper. I can see where poor phrasing on my part could cause confusion.