I'm using a BLL that has a Typed DataSet which accesses an SQL Database via a
Connection String. The Connection String is set in the Application Settings
with Type = (Connection String)

When I add the BLL assembly to an ASP.NET Web Application, I want the BLL to
get the Connection String from Web.Config. This becomes an issue when going
from development, to staging to production.

Is there a strategy to set the Connection String in the BLL Assembly's
Application Settings so that the BLL DLL can be moved from development to
Staging to Production without a recompile just to change the Connection
String in the Application Settings?

TIA
g

If the BLL has a reference to System.Web, and System.Configuration, then it
should be able to read the ConnectionStrings element just like a web page in
the web would do.
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com



"geogruven" wrote:

> I'm using a BLL that has a Typed DataSet which accesses an SQL Database via a
> Connection String. The Connection String is set in the Application Settings
> with Type = (Connection String)
>
> When I add the BLL assembly to an ASP.NET Web Application, I want the BLL to
> get the Connection String from Web.Config. This becomes an issue when going
> from development, to staging to production.
>
> Is there a strategy to set the Connection String in the BLL Assembly's
> Application Settings so that the BLL DLL can be moved from development to
> Staging to Production without a recompile just to change the Connection
> String in the Application Settings?
>
> TIA
> g