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


i reading asp.net core features , decide transfer current solution ( mvc 5 ) mvc 6 got little bit confused regarding integrated di. have architecture

current architecture

cemamanager ( representative layer ) has reference helpers, resource, viewmodel , bll. bll has reference viewmodel, database , dll. dll has reference database.

typical n-tier architecture using di , repository pattern.

when investigate mvc6 there startup.cs di initialize. means if want separate bll , dal have reference mvc6 , logic go thru layer? time it's gonna heavy , hard maintain , scale or wrong?

is there way export startup.cs or di method layer? maybe know articles read or examples?

personally have few things change overall structure, i'm guessing full design review isn't you're asking for. on actual question, no - other layers not need reference mvc.

for application, ioc needs configured , initialized in presentation layer. presentation layer needs reference chain (direct or indirect references) want register, has been true.

you referencing helpers, resource, viewmodel, , bll can register implementations interfaces in layers. add reference dll register implementations layer.

you can go indirect route , add class in each layer takes reference ioc container , handles own registration. in autofac done using modules there equivalent ways of accomplishing same thing using other ioc containers.


Comments

Popular posts from this blog

java - Suppress Jboss version details from HTTP error response -

gridview - Yii2 DataPorivider $totalSum for a column -

Sass watch command compiles .scss files before full sftp upload -