Here is the solution I came up with: create own MembershipProvi der.
Sounds like a lot of work, doesn't it? Well, actually it does not have to be
created from scratch.
How about altering slightly the behavior of the existing
SqlMembershipPr ovider, so instead of using the predefined connection string
it grabs the one I specify dynamically, in my case based on the host name?
Here is how simple it is:
class MyMembershipPro vider : SqlMembershipPr ovider
{
public override void Initialize(stri ng name, NameValueCollec tion config)
{
config["connectionStri ngName"] = ConnectionStrin g.Name;
base.Initialize (name, config);
}
}
And for the completeness:
public static string ComputerName {
get {
if (System.Web.Htt pContext.Curren t == null) {
return System.Windows. Forms.SystemInf ormation.Comput erName;
} else {
return System.Web.Http Context.Current .Server.Machine Name;
}
}
}
public static ConnectionStrin gSettings ConnectionStrin g {
get {
ConnectionStrin gSettings connectionStrin g = null;
connectionStrin g = ConfigurationMa nager.Connectio nStrings[ComputerName+
"ConnectionStri ng"];
if (connectionStri ng == null) {
connectionStrin g =
ConfigurationMa nager.Connectio nStrings["DefaultConnect ionString"];
}
return connectionStrin g;
}
}
Now I can define several connection strings in the config
<connectionStri ngssection, each for the host/environment where I plan to
install my application, and one default MembershipProvi der of the
MyMembershipPro vider type with empty connection string. Example:
<connectionStri ngs>
<add name="SomeHost1 ConnectionStrin g" connectionStrin g="..."/>
<add name="SomeHost2 ConnectionStrin g" connectionStrin g="..."/>
<add name="DefaultCo nnectionString" connectionStrin g="..."/>
</connectionStrin gs>
<membership defaultProvider ="DefaultMember shipProvider">
<providers>
<add name="DefaultMe mbershipProvide r" type="MyMembers hipProvider"
connectionStrin gName="" applicationName ="MyApplication "/>
</providers>
</membership>
Now, when the time comes and ASP.Net initializes my customized default
provider the provider will choose the right connection string itself.
The solution can be further extended, but it perfectly works for me as it
is, so I decided to post it here.
Tomasz
