The company I work for recently purchased the sub domain add-on functionality for our website, but I think it wasn't what we needed. What we're trying to get is four separate websites to uses a staging areas (development, test, staging and prod of our website). I wrote a url redirection http module similar to the code provided in the sub domain start-up thread but ran into an issue: each of the websites has it's own authentication/authorization scheme. Having a folder called development (set as a web application via the DASP IIS tool) under the root website still means that the membership provider for dev's parent is still being used along with the membership provider set up in dev. What I'm looking for is the correct mechanism for setting up 4 distinct websites that can be accessed using a subdomain.
Hi, If you are in need of Authentication for 4 different sites using applications I believe you will need 4 sites. You can combine the Control Panels and you can redirect to any of the 4 from one that way. There are ways to do this on one site, for example 4 forum packages can be on the same site and require login independent of each other. But to do this with ASP.NET Authentication from one site root to 4 independent folders will be a nightmare. Maybe someone else will have an idea or two for you but this is my 'opinion' on the matter. All the best, Mark
