Joe,
What you are suggesting is basically 3 different web sites, running 3
different applications. Sure, they may be using the same code, but as far
as IIS goes they are as different as any 3 other websites. Just think of it
as setting up 3 different web sites in IIS, regardless of the code that runs
in each.


"Joerg Schrocke" <speedy1179 (AT) web (DOT) de> wrote

It seems to me like this really the hard way of going about things.

It sounds like you have one web application but you have thre
different databases (one for each project). I assume that over tim
you'll add more projects, at which point you'll create a new databas
and add another copy of your web app to the web server.

Wouldn't it be easier and more maintainable to only have one copy o
your application running on the IIS box, but use different host header
to access it?

In IIS you can configure just about as many host-headers as you wish
assigning a name and an IP address to each.

So, it'd look something like this.

IIS:
IP: Some IP Host Header: project1.yourdomain.com
IP: Some IP Host Header: project2.yourdomain.com

Then slap some keys in your web.config file for each project...

Something like this...
<add key="HostHeader.Project1" value="project1.yourdomain.com"/>
<add key="HostHeader.Project2" value="project2.yourdomain.com"/>

You'll need to put a connection string property in your web.config fo
each of those keys as well...

When you get to the point where you would normally grab the connectio
string from the config, first grab the host header, here is the cod
for that...

string strHostHeader
HttpContext.Current.Request.ServerVariables["HTTP_HOST"].ToLower().Trim();

Then just grab the connection string for that host header...

I just finished reading what I wrote, that got pretty long, boring da
at work...

Mik

--
manger2