拆分/模块化大型ASP.NET Web应用程序项目 [英] Splitting / Modularizing Large ASP.NET Web Application Projects

问题描述

我们的公司有一个相当大的ASP.NET Web应用程序。该应用程序已经分成业务功能不同的区域。我在寻找一些策略，我们可以利用这个Web应用程序分成单独的可建/版本控制模块。

Our company has a fairly large ASP.NET web application. The app is already broken up into distinct 'areas' of business functionality. I'm looking for some strategies we can use to split this web application into separate buildable/versionable modules.

主要目标是为：

让我们只用功能选择区部署Web应用程序。

Enable us to deploy the web app with only select areas of functionality.

我设想父Web应用程序作为一个外壳，可容纳插件，可以自己作为父Web应用程序的导航层次结构的菜单项注册。父Web应用程序将包含母版页，样式表和常用控件的插件使用。

I envision the parent web app as a 'shell' that can host 'plugins' which can register themselves as menu items on the parent web app's navigation hierarchy. The parent web app would contain the master page, stylesheets and common controls used by the plugins.

什么样的​​想法你有实现这样的事情？

What kinds of ideas do you have for implementing something like this?

推荐答案

我会做子网站的项目。每个网站是父网站的一个子项目。您可以编写一些检查的数据存储，看是否有客户访问该网站（模块），并拒绝以这种方式获得一个HttpModule。斯科特格思里有一个很好的一篇关于如何设置子Web项目<一个href=\"http://weblogs.asp.net/scottgu/archive/2006/08/16/tip_2f00_trick_3a00_-creating-sub_2d00_web-projects-using-the-vs-2005-web-application-project-option.aspx\">here.

I would do sub-web projects. Each website is a sub-project of the parent website. You can write an HttpModule that checks some data store to see if that customer has access to that site (module) and deny access in that way. Scott Guthrie has a nice post about how to set up sub web projects here.

这篇关于拆分/模块化大型ASP.NET Web应用程序项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！