设计一个Asp.Net应用支持子网站 [英] Designing an Asp.Net App that supports SubSites
问题描述
我设计必须支持子网站的ASP.Net应用程序。
I'm designing an ASP.Net application that must support 'SubSites'.
这个想法是有一个超级管理员管理所有用户，全局应用程序设置和子网站。每个子网站都有一些自己的设置（如本地管理员，标识和欢迎留言），每个子网站都有自己的注册用户列表。
The idea is to have a super admin manage all users, global application settings and SubSites. Each Subsite has a few of its own settings (such as a local admin, logo and welcome message) and each SubSite has its own list of registered users.
这是和您使用的CMS如Joomla，或的SharePoint DotNetNuke的东西非常相似。其实，我很想用这样一个平台，但其他项目的要求$ P $做那pvent我。
This is very similar with what you get using a CMS such as Joomla, SharePoint or DotNetNuke. In fact, I'm tempted to use such a platform, but other project requirements prevent me from doing that.
我的问题是非常普遍的在这一点上：
My questions are very general at this point:
- 使用 ASP.NET 2.0会员，如何会我指定一个超级管理员，并根据他们所注册？子网站用户分类
- 我将如何实现子网站（应该用什么图案等）？我在解释其他人如何做这个文章特别感兴趣。我想学习别人已经获得的最佳实践，而无需花费几天挖掘到像DotNetNuke的大型开源项目的源$ C $ C。
- Using ASP.NET 2.0 Membership, how would I designate a super admin and classify users based on the SubSite in which they have registered?
- How would I implement SubSites (what patterns should be used, etc)? I'm especially interested in articles that explain how others have done this. I would like to learn the best practices that others have acquired, without spending days digging into the source code of a large open source project like DotNetNuke.
我会在ASP.Net MVC 1.0来实现这一点，所以在这方面任何的例子将是最有帮助的。
更新：
我真的很喜欢迈克哈德洛如何实现多租户，我已经决定用他的作品为出发点。见<一href=\"http://stackoverflow.com/questions/922891/inject-a-membershipprovider-into-asp-net-mvc-accountcontroller\">this帖子的信息对我如何使用SqlMembershipProvider的，每个租户有自己的孤立的数据库。这解决了我的会员资格的基础上的子网站的问题。
I'll be implementing this in ASP.Net MVC 1.0, so any examples in that regard will be most helpful.
UPDATE: I really like how Mike Hadlow implemented multi-tenancy and I've decided to use his work as a starting point. See this post for info on how I'm using SqlMembershipProvider with each tenant having their own isolated database. That solves my membership "based on subsite" problem.
推荐答案
什么你试图更通常被称为的多重任务处理，而不是子网站
What you're attempting is more commonly referred to as "multitenancy", not "subsites"
有一个<一个href=\"http://stackoverflow.com/questions/483414/converting-single-db-asp-net-site-into-multitenant-membership-and-roles-dilema\">similar问题此，并且接受的答案听起来很有道理的。
There was a similar question to this, and the accepted answer sounds plausible.
这篇关于设计一个Asp.Net应用支持子网站的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
