Dependency Injection with Entity Framework - Connection Strings

Question

Im currently creating a middle tier layer for editing rules for an application. The data access is handled using entity framework and a repository class. My manager has suggested to inject the connection string for the database down to the repository class and I'm confused as to his thinking behind this?

Is there any need for this and what benefits would it provide?

Thanks

user · Accepted Answer · 2013-08-13 15:20:01Z

1

Dependency injection gives you freedom of changing the string when for example unit testing. In your case, I believe you would be better of mocking the database instead, but if you have a test database that is to be used instead of a mock, that lets you change a connection string when instanciating the object.

answered Aug 13, 2013 at 15:20

user

7198 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Steve2056726 Over a year ago

Isnt the purpose of it being stored in the App-Config so it can be changed easily?

user Over a year ago

Sure, if you have another solution configuration that is complete. But if you have a set of tests that are to test your services using an in-memory database, then it would make sense.

Collectives™ on Stack Overflow

Dependency Injection with Entity Framework - Connection Strings

1 Answer 1

2 Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Related