I have an ASP.NET application. I want to be able to invsibly rollout new versions to our customers (all users logon). I want an "old" site and a "new" site.
The user has one url. Once they are authenticated, they are sent either to the "old" or the "new" site depending on their database version.
Is this possible with IIS 7? How best to do it?
Windows IIS test server setup
How to configure multiple intranet website on server 2003?
Dojo load time extremely slow on iis
I'm presuming users logon via forms authentication, and that determining the users database version is trivial?.
bypass IIS xml file settings at file/folder level
If so then you can simply host your old and new version in separate virtual directories then make sure they can share authentication cookies.
Creating IIS Instance over network using MSBuild
Once the user is successfully verified ( presumably on the new version of the site) if they should be using the old site you redirect them to the default page of that site instead of the new version.
is it possible to install IIS 7 on windows XP?
I believe the mehod to do the redirect in is RedirectFromLogonPage().
IIS, Impersonation and COM Interop. Permission Denied
In addition to prevent the user from using a bookmark to go to the wrong site you could put something in the
Global.asaxthat does a lookup of the base URL the user should be using and redirect their request appropriately, you'd have to do that in both the new and OLD versions of the site though..
Can't read query string if default index file name is omitted?