ASP.NET Core AddContext

Question

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!

No Refunds No Returns · Accepted Answer · 2018-12-18 03:18:40Z

4

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?

edited Dec 18, 2018 at 3:18

No Refunds No Returns

8,4464 gold badges36 silver badges44 bronze badges

answered Dec 17, 2018 at 16:29

CodeCaster

153k24 gold badges237 silver badges287 bronze badges

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

1 Comment

Charles Schneider Over a year ago

OK. Maybe I don't really understand what does it mean. But in a simple 3-tier app, for instance, I shouldn't have web, service and data layer, on which web gets its data through service layer, and service gets its data from data layer (which actually contains dbcontext reference)?

Collectives™ on Stack Overflow

ASP.NET Core AddContext

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related