This would be something that 2003 server and ASP.Net would use, ie, another
section of the IIS whereas you could manage connection strings and such via
a more common admin console, and allow ASP.Net to dole it out to the app via
some static function like

IDbConnection ApplicationInstance.GetDbConnection("key1")

so you would see in an admin console:

[-] AspnetApp1
[-] Database connections
[ ] SqlConnection1
[ ] Type: SqlConnection
[ ] ConnectionString: "server=localhost..."

the key to maintain the XCOPY deployment is to establish a section in
web.configs, defined in the machine.config, of the application db
connections:

<system.web>
<dbconnectionpool>
<dbconnection key="SqlConnection1"
type="System.Data.SqlClient.SqlConnection"
connectionString="server=localhost;uid=sa;pwd=supe rsecretSaPwd" />
</dbconnectionpool>
</system.web>

Now, in your ASPNet apps, or even Data tier projects,
a call to System.Web.Application.GetDbConnection("SqlConnect ion1",
[opened=]true ) would give you a opened IDbConnenction that could be casted
to a SqlConnection [since thats what the app expects]

Is this admin overkill I wonder?


--
Eric Newton
[email]eric@ensoft-software.com[/email]
C#/ASP.net Solutions developer