Why When use IoC in MVC Application?

Question

I have general questions

1) Why we need IoC in Asp.NET application ?

2) When should use it

3) if I dont use Structuremap in my MVC Application What will I miss?

Unfortunately I have problems with the DI so Please explain in simple

For number 3, are you asking what you'll miss if you don't use an IoC container or what StructureMap provides that others don't? — jmcilhinney, Apr 01 '14 at 06:09
Related: https://stackoverflow.com/questions/130794/what-is-dependency-injection — Steven, Apr 01 '14 at 06:13

jmcilhinney · Answer 1 · 2014-04-01T06:19:12.563

You don't need it. Using it provides advantages but it's not required.
When creating instances of types from a lower layer, e.g. a controller creating a service or a service creating a repository.
Mainly IoC helps to decouple the layers. For instance, we are creating an application where the service layer is a DLL in the same folder as the web site. There's a chance that it will later be broken out into a web service. Because the web site uses IoC to create the service objects, that change will not require any adjustment to the code of the web site. We can simply change the IoC configuration and it will just work.

score 0 · Answer 2 · answered Apr 01 '14 at 06:37

Bacause it is a good practice. Code is much clearer and easier to maintenance.
For example i'm using it in controllers constructors (i pass repositories and services as arguments) and in repositories (i pass dbcontext as argument) - but it depends on your project's architecture.
StructureMap is one of the Ioc containers (i personally prefer NInject or Funq) so without it you miss all advantages of using IoC.

2 Answers2