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.
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:
- 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.
I’m implementing this in ASP.NET MVC 1.0, so similar examples will be most helpful.
UPDATE:
I 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”
There was a similar question to this, and the accepted answer sounds plausible.