I have one dll containing my entire mvc app running on iis7 server. Should I instead have compiled controllers and business logic into separate dll's? Furthermore, should I install the non controller dll's in a separate server and if so do I configure a new virtual directory to the remote server?
我有一个dll包含在iis7服务器上运行的整个mvc应用程序。我应该将控制器和业务逻辑编译成单独的dll吗?此外，我应该在单独的服务器上安装非控制器dll吗?如果需要，我应该为远程服务器配置一个新的虚拟目录吗?
What is the typical practice here? Thanks
这里典型的做法是什么?谢谢
1 个解决方案
#1
2
I guess that depends on your business needs, but in general I am a fan of modularity. We have our Model shared between multiple sites so it is in its own DLL and the controllers etc. for each site are generally in another (for each site) and additional add-ons in their own as well.
我想这取决于您的业务需求，但总的来说，我喜欢模块化。我们的模型在多个站点之间共享，所以它在自己的DLL中，每个站点的控制器通常都在另一个站点(每个站点)中，另外的附加组件也在它们自己的站点中。
Compiling into one DLL would probably get you a performance increase, but you would be hurt when it comes to upgrading individual modules.
编译成一个DLL可能会提高性能，但是当涉及到升级单个模块时，您会受到伤害。
#1
2
I guess that depends on your business needs, but in general I am a fan of modularity. We have our Model shared between multiple sites so it is in its own DLL and the controllers etc. for each site are generally in another (for each site) and additional add-ons in their own as well.
我想这取决于您的业务需求，但总的来说，我喜欢模块化。我们的模型在多个站点之间共享，所以它在自己的DLL中，每个站点的控制器通常都在另一个站点(每个站点)中，另外的附加组件也在它们自己的站点中。
Compiling into one DLL would probably get you a performance increase, but you would be hurt when it comes to upgrading individual modules.
编译成一个DLL可能会提高性能，但是当涉及到升级单个模块时，您会受到伤害。