Multiple sites, single application

(under ASP.Net)
when running multiple web sites with same code but different front-end and
content (database), I guess the common way is to have multiple hostings. I'm
wondering if somebody does it differently, like having one host (web
application) but different DB connection strings and MasterPage (2.0), set
somewhere in the Pre_Init event handler. This way you only pay for one
hosting and you only have to upload new/changed code once.

Is someone familiar and using with this "trick" ?

Depends on whether you own the website's bindings or not.

Suppose you pay for www.website1.com which hosts your web application that
has multiple front ends, one of which is supposed to handle www.website2.com

When someone types http://www.website2.com , how is that request going to
find its way to your multiple front end web application that answers to
www.website1.com?

If you control the website binding, you can simply add www.website2.com to
the binding, add your Pre_Init code (or however you are going to do this),
add DNS entry to point www.website2.com to the IP of your website, and it
should work.

If you do not control the website binding, then you need to figure out a way
to get that request to your multi front end web application.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Daves" <dbspam RemoveThis @simnet.is> wrote in message
news:%23WhFyUwUFHA.2468@TK2MSFTNGP10.phx.gbl...
(under ASP.Net)
when running multiple web sites with same code but different front-end and
content (database), I guess the common way is to have multiple hostings. I'm
wondering if somebody does it differently, like having one host (web
application) but different DB connection strings and MasterPage (2.0), set
somewhere in the Pre_Init event handler. This way you only pay for one
hosting and you only have to upload new/changed code once.

Is someone familiar and using with this "trick" ?