M
MyFavoriteMartian
I have a web site, and I want to plan for adding different versions while keeping the initial version online.
The main web site will always be used as an entry point,
and if a customer or user is configured to use a different version,
they would be redirected to it.
I want to be able to add new versions or make changes to existing versions without
causing the main application to restart.
I was thinking an application under the main web, with it's own application pool would accomplish this,
but I'm having trouble configuring the sub web site application.
For example:
https://main is the primary web site/application.
I would create an application under //main called V2.
I would want the main application to redirect users after login to //main/V2
Can some advise on how to configure the V2 application to behave like
it is part of //main, but without being disruptive to //main when
changes are made to V2.
Thank you
Continue reading...
The main web site will always be used as an entry point,
and if a customer or user is configured to use a different version,
they would be redirected to it.
I want to be able to add new versions or make changes to existing versions without
causing the main application to restart.
I was thinking an application under the main web, with it's own application pool would accomplish this,
but I'm having trouble configuring the sub web site application.
For example:
https://main is the primary web site/application.
I would create an application under //main called V2.
I would want the main application to redirect users after login to //main/V2
Can some advise on how to configure the V2 application to behave like
it is part of //main, but without being disruptive to //main when
changes are made to V2.
Thank you
Continue reading...