使用ASP.NET 5的N层架构（MVC 6）(N-Tier Architecture using ASP.NET 5 ( MVC 6 ))

 我正在阅读有关ASP.NET核心功能的内容，我决定将当前的解决方案（MVC 5）转移到MVC 6，但我对集成DI有点困惑。 目前我有这个架构 
 
  
 
 CemaManager（代表层）引用了Helpers，Resource，ViewModel和BLL。 Bll引用了ViewModel，Database和DLL。 Dll引用了Database。 
 
 使用DI和存储库模式的典型N层架构。 
 
 当我调查MVC6时，有启动器，其中DI初始化。 这意味着如果我想分离BLL和DAL，它们将全部引用MVC6并且所有逻辑都将通过该层？ 到时候它会变得沉重，难以维持和扩展，还是我错了？ 
 
 有没有办法将startup.cs或DI方法导出到另一层？ 也许有人知道要阅读的文章或例子？ 

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? 

原文：https://stackoverflow.com/questions/38460281