How to configure the ASP.NET 2.0 Membership/Roles Provider Problem and Work Around

I seem to have been having the same problem as everyone else.


I read the knowledgebase article...


http://support.discountasp.net/KB/a337/how-to-configure-aspnet-20-membershiproles-provider.aspx?KBSearchID=10046


did this <remove name="LocalSqlServer" /> and assumed that my previous connection string that I had created when the site was being hosted locally would work.


The above article indicated that this was the case and that I was not limited to having to name the connection string "LocalSqlServer".
However it did not. In the end I simply created a duplicate connection string that was the same as my previous one and named it LocalSqlServer and it now works. So I now have two connection strings both the same but with 2 different names. This also saved me doing a global find and replace for all my connection strings referencesin my app.


Intellectually I find the solution somewhat irritating but it works.

If anyone can tell why this is the case let me know?

 

I think maybe you're assuming that just by specifying a connection string, that the application would use it. This is not the case. The ASP.NET membership providers use "LocalSqlServer" as the default connection string. So unless you customize the provider and specify a different connection string to use, then it will continue to use "LocalSqlServer".




Aristotle

DiscountASP.NET
www.DiscountASP.NET