How can I change the connection string for a Membership Provider in the Global.asax file?

[Alias]

Hi -

I have a site that runs on a development and production server. I'd like to
programmaticall y change the connection string the provider uses in the
web.config file and have the provider use the updated string. I am able to
successfully change the string using this code in the Application_Sta rt
method of the Global.asax file:

Dim csNew As ConnectionStrin gSettings

Dim config As Configuration =
System.Web.Conf iguration.WebCo nfigurationMana ger.OpenWebConf iguration(HttpC ontext.Current. Request.Applica tionPath)

csNew = New
ConnectionStrin gSettings(confi g.ConnectionStr ings.Connection Strings("conn") .Name,
"cstring",
config.Connecti onStrings.Conne ctionStrings("S PIncConn").Prov iderName)
If (config.Connect ionStrings.Conn ectionStrings(" conn").Connecti onString <>
"correct cstring") Then
config.Connecti onStrings.Conne ctionStrings.Re move("conn")
config.Connecti onStrings.Conne ctionStrings.Ad d(csNew)
config.Save()
End If

After this runs I can open the web.config and see the correct
connectionStrin g entry is in it. So that is working. However when I try to
log in the Membership system in ASP.Net is still hooked up to the old
database somehow. From what I've read I figured maybe the config.Save()
method would cause an app restart which would in turn cause the Membership
stuff to sync with the new database. The connectionStrin gName propery in my
provider doesn't need to change because when I alter it I'm using the same
name.

I think this is being cached somewhere. The weirdest part is if I go into
IIS, stop the app, then restart it, it is still hooked up to the wrong DB
even though I can physically open the web.config and see that it is now
holding the correct string for that server. However if I physically reboot
the whole server it then notices the new string and works just fine.

Does anyone know where this would be cached or stored outside of the
application itself? When I run locally through VS.Net 2005 this works like
a charm. It isn't a permission issue with modifying the web.config because
I can see that the file is being modified successfully on the server.
Thanks for any insight!