CODEWITHSUNDEEP
asp.net-coreentity-framework-coredbcontext
Charles Schneider
Charles Schneider

Reputation: 1

ASP.NET Core AddContext

I'm architecting a new App and I really unconfortable with this approach in ASP.NET Core that made "normal" adding a DbContext by using AddDbContext, in services.

I'd like to know if you guys think that using AddDbContext in ASP.NET Core isn't a bad practice, since it forces my Web App to have a dependecy on my database access layer.

I've researched a lot and it was incredible that there isn't almost anything that cover this subject.

How should I proceed to overcome this concern?

Thanks!

Upvotes: 0

Views: 461

Answers (1)

CodeCaster
CodeCaster

Reputation: 151588

it forces my Web App to have a dependency on my database access layer

That's exactly the place where it should be: the composition root. Your application startup code is the place where you glue your components together.

What else would you want, create a separate library, containing interfaces for all classes in your entire DAL, and wire that up using magic during startup?

Upvotes: 4

Related Questions