N-Tier Architecture using ASP.NET 5 ( MVC 6 )

Question

I was reading about ASP.NET Core features and I decide to transfer my current solution ( MVC 5 ) to MVC 6 but I got a little bit confused regarding integrated DI. Currently I have this architecture

CemaManager ( representative layer ) has reference to Helpers, Resource, ViewModel and BLL. Bll has reference to ViewModel, Database and DLL. Dll has reference to Database.

Typical N-tier architecture using DI and Repository pattern.

When I investigate MVC6 there is startup.cs where DI initialize. That means if I want to separate BLL and DAL they will have all reference to MVC6 and all logic will go thru that layer? By the time It's gonna be heavy and hard to maintain and scale or am I wrong?

Is there any way to export startup.cs or DI method to another layer? Maybe somebody know any articles to read or examples?

Answer 1

Personally I have a few things I would change about the overall structure, but I'm guessing a full design review isn't really what you're asking for. ON your actual question, no - your other layers do not need to reference MVC.

For most any application, IoC needs to be configured and initialized in the presentation layer. Ultimately your presentation layer needs a reference chain (direct or indirect references) to everything you want to register, but this has always been true.

You are already referencing Helpers, Resource, ViewModel, and BLL so you can easily register implementations for the interfaces in those layers. You could also add a reference to DLL to register implementations from that layer.

You can also go the indirect route and add a class in each layer which takes a reference to your IoC container and handles its own registration. In Autofac this is done using modules but there are equivalent ways of accomplishing the same thing using other IoC containers.