Franklin, I've done something very similar in the past also - which is why I am leaning that way now.
Something else I considered doing (because this app isn't just for the ASP - I need to run it here and I don't have the multi-tenanted problems like they do) was writing a "NetTech.Configuration" namespace, from which I return a connection string and a tablename prefix. Then, for my local version for me I write this namespace to simply return the connection string and table prefix from the app.config. Then, for the ASP version I write one which queries AD to get the company name, then uses the connection string in the app.config to connect to the common database, and retrieve the connection string for this users company etc. I'm hoping that I can write an assembly with many different "versions" and have them just "droppable" - i.e. place the same exe on all computers, but put a different "NetTEch.Configuration" assembly depending on the type of connection they require... Just a thought at this stage... Dino -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of franklin gray Sent: Thursday, 23 May 2002 09:50 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Multi-tennanted apps. Dean: We have the same issues you do when we start to host our app. However, my boss says that our clients will not share a DB. So what we have decided to do is have a public Web Serivce where all calls are made. When a user logs into the system, part of the user profile is to say what server and what DB he belongs to. Of course all users will have to be in a common/master DB on one server. Part of the user profile that we send back to the client is the server and DB names. When the client makes additional Web Service calls, the server and DB name will be passed. I don't know if this is the best approach, but it solves the issue of hosting apps to companies that want their data in a seperate DB. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.363 / Virus Database: 201 - Release Date: 21/05/2002 You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
