I store the connection strings for all three of my environments (development, test, production) in the “connectionstrings” section of web.config on most of my ASP.NET Web applications. When deploying the app to one of these environments, I either have to change a key called “Environment” in the appSettings section of web.config, or I can just put it in machine.config on the server. Connection strings:
Setting the connection string attribute on a SqlDataSource control can be done in a number of ways. It can be programmatically done in the code-behind file, and this is the way it is most often done dynamically. This is not always convenient, as you may have to spend lots of time determining the event during which the string must be set.
SqlDataSource1.ConnectionString = System.Configuration.ConfigurationManager.ConnectionStrings("whatever")
For instance, if the SqlDataSource control is embedded inside the EditTemplate of a FormView control, it will not be accessible during Page.Load, and if a parameter of the SqlDataSource control is databound, you may have to navigate a Byzantine maze of ASP.NET lifecycle events to find out that it needs to be set in the Load event of some seemingly unrelated control.
To solve this problem, many people give up and use only one active connection string at a time in web.config, and comment the others out:
Then, “dynamically” setting the string in the SqlDataSource markup like this:
This works fine, but will require a change in the connection string in web.config to move from one environment to another. At first, I assumed (and we all know what that does!) that one could dynamically set the attribute using the standard inline < %= %> notation like this:
" SelectCommand="sp_SourceSelectAllChildren" SelectCommandType="StoredProcedure">
Anyone who has tried this already knows what happened next. This caused a run-time error when the SqlDataSource tried to bind to the expression. After much wailing and gnashing of teeth, I found that it IS possible to dynamically set the connection string in a manner similar to the standard way! Instead of the < %= %> expression, a custom expression using the < %$ %> notation will work.
First, to build the custom expression in a class:
Imports System Imports System.CodeDom Imports System.Web.UI Imports System.ComponentModel Imports System.Web.Compilation ' Apply ExpressionEditorAttributes to allow the ' expression to appear in the designer.
_ _ Public Class ConnStringExpressionBuilder Inherits ExpressionBuilder ' Create a method that will return the result ' set for the expression argument. Public Shared Function GetEvalData(ByVal expression As String, _ ByVal target As Type, ByVal entry As String) As Object Return System.Configuration.ConfigurationManager.AppSettings("Environment") & "_" & _ System.Configuration.ConfigurationManager.ConnectionStrings("whatever") End Function Public Overrides Function GetCodeExpression(ByVal entry _ As BoundPropertyEntry, ByVal parsedData As Object, ByVal context _ As ExpressionBuilderContext) As CodeExpression Dim type1 As Type = entry.DeclaringType Dim descriptor1 As PropertyDescriptor = _ TypeDescriptor.GetProperties(type1)(entry.PropertyInfo.Name) Dim expressionArray1(2) As CodeExpression expressionArray1(0) = New CodePrimitiveExpression(entry.Expression.Trim()) expressionArray1(1) = New CodeTypeOfExpression(type1) expressionArray1(2) = New CodePrimitiveExpression(entry.Name) Return New CodeCastExpression(descriptor1.PropertyType, _ New CodeMethodInvokeExpression(New CodeTypeReferenceExpression _ (MyBase.GetType()), "GetEvalData", expressionArray1)) End Function End Class
Next, in your web.config file, add this to the compilation section:
Lastly, change the ConnectionString attribute in the markup for the SqlDataSource control to:
You can now have multiple connection strings declared in the web.config, and set them dynamically in your markup rather than in the code-behind.
Note: What goes after the “ConnStringExpression:” is incidental in this case; I just put “AppDB” for readability purposes.