Best way to manage connection strings in a project containing both Classic ASP and ASP.Net 1.1 code?

Posted by JamesEggers on Stack Overflow See other posts from Stack Overflow or by JamesEggers
Published on 2009-10-22T21:25:11Z Indexed on 2010/04/22 6:23 UTC
Read the original article Hit count: 287

I have a project that I have inherited that is primarily a Classic ASP application; however, intermixed in the the application are a handful of ASP.net pages. Some of the ASP.net pages are 1.1 and do not use a code behind model.

The classic ASP pages have a number of /include directories where there's a file for database connections. The ASP.Net pages have the connection string hard coded in in their code.

I'm trying to clean up this mess of connection strings so it's easier to manage across development environments.

Does anyone have any recommendations on how I may be able to effectively do this that will work for both Classic ASP and ASP.Net pages?

Thanks

© Stack Overflow or respective owner

Related posts about subjective

Related posts about ASP.NET