Asp.net, C#, .NET MVC

Question

1.00/5 (2 votes)

See more:

which design pattern do you implement in order to improve unit testing in your code by loosely coupling object dependencies through object constructor arguments?
1-adapter
2-Dependency Injection
3-Abstract Factory
4-Observer
5-Singleton

What I have tried:

which design pattern do you implement in order to improve unit testing in your code by loosely coupling object dependencies through object constructor arguments?
1-adapter
2-Dependency Injection
3-Abstract Factory
4-Observer
5-Singleton

Posted 29-May-17 18:50pm

Member 13230054

Updated 29-May-17 20:52pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 13230250 · Answer 1 · 2017-05-29T20:52:00

Answer:Dependency Injection

Dependency Injection (DI), also more cryptically known as "Inversion of Control" (IoC), can be used as a technique for encouraging this loose coupling. There are two primary approaches to implementing DI: constructor injection and setter injection. Obviously, at some point, something must be responsible for creating the concrete objects that will be injected into another object. The injector can be a parent object, which I'll call the "DI controller", or can be externalized and handled by a "DI container" framework.