I've done a large study into using MVC and thanks to the people here a lot of the issues revolving around it have been cleared up for me.
我已经做了很多关于使用MVC的研究,感谢这里的人们,围绕它的许多问题已经为我清理了。
The problems I'm having now revolve around the sheer size of our application and how it would be organised within the project itself. For example, we have url's such as http://mylocalapp/folder/nestedfolder/subfolder/theapp. The reason we do this is because the application quite literally is that large. We need that kind of folder structure because otherwise the application would be unmanageable.
我现在遇到的问题围绕着我们的应用程序的庞大规模以及它在项目本身中的组织方式。例如,我们有url,例如http:// mylocalapp / folder / nestedfolder / subfolder / theapp。我们这样做的原因是因为应用程序确实很大。我们需要这种文件夹结构,否则应用程序将无法管理。
Phil Haack covers the registering of routes for nested folders in one of his blog posts which is very useful indeed, but our application has sub-applications and sub-applications within that. It couldn't be simplified any further.
Phil Haack在他的一篇博文中介绍了嵌套文件夹路由的注册,这非常有用,但我们的应用程序中有子应用程序和子应用程序。它无法进一步简化。
What steps need to be taken to manage such a large application which spans a large amount of folders and has folders up to seven levels deep, as well as having about 15 databases? Is MVC really the answer for an application of this size?
需要采取哪些步骤来管理这样一个跨越大量文件夹并且文件夹深达七层的大型应用程序,以及大约15个数据库? MVC真的是这个尺寸应用的答案吗?
Is another option simply to apply lots of URL routing and map route areas for all the separate sub-folders?
另一种选择只是为所有单独的子文件夹应用大量的URL路由和地图路由区域?
3 个解决方案
#1
If you don't need to have everything inside of one application, why not create an MVC application in each folder?
如果您不需要在一个应用程序中包含所有内容,为什么不在每个文件夹中创建MVC应用程序?
#2
I have a similar situation and what we did was instead of making a "fat" controller, we make them "skinny". Ian Cooper has an excellent write-up here.
我有类似的情况,我们做的不是做一个“胖”控制器,我们让它们“瘦”。 Ian Cooper在这里写得非常好。
So what we did is we broke down the "sub-applications" to be its own application. I think this is what the previous posters trying to convey as well.
所以我们所做的就是将“子应用程序”分解为自己的应用程序。我认为这也是之前海报试图传达的内容。
#3
As per a comment "Are you refering to "Areas"?" was the answer eventually.
根据评论“你是指”领域“吗?”最终是答案。
#1
If you don't need to have everything inside of one application, why not create an MVC application in each folder?
如果您不需要在一个应用程序中包含所有内容,为什么不在每个文件夹中创建MVC应用程序?
#2
I have a similar situation and what we did was instead of making a "fat" controller, we make them "skinny". Ian Cooper has an excellent write-up here.
我有类似的情况,我们做的不是做一个“胖”控制器,我们让它们“瘦”。 Ian Cooper在这里写得非常好。
So what we did is we broke down the "sub-applications" to be its own application. I think this is what the previous posters trying to convey as well.
所以我们所做的就是将“子应用程序”分解为自己的应用程序。我认为这也是之前海报试图传达的内容。
#3
As per a comment "Are you refering to "Areas"?" was the answer eventually.
根据评论“你是指”领域“吗?”最终是答案。