Problem with Membership Providers in 4.20.19

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
Posts: 11
Joined: Mon 20 Nov 2006 19:27

Problem with Membership Providers in 4.20.19

Post by badgeratu » Thu 27 Sep 2007 14:32


With the release of 4.20.19 it seems that an old bug has resurfaced. In an existing project I have defined an ASP.NET Membership Provider in a site Web.config file as follows:

This has worked for some time now, however with the release of 4.20.19 an error is thrown when the provider is loaded indicating that "ApplicationName" is an unrecognized attribute.

This was a problem that was resolved in an earlier version of MySQL Direct (I forget which one), and it seems that your provider is no longer informing the System.Configuration layer that "ApplicationName" is a valid attribute. This prevents the provider from being loaded, or (by omitting ApplicationName) from locating the correct Membership Application group in the database.

This is a MAJOR BUG that has been re-introduced. Can you please resolve it ASAP, or suggest a workaround? (as setting the ApplicationName property in code does not work when the membership provider is dynamically invoked).

Simon Jones

Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 27 Sep 2007 14:50

The correct spelling is "applicationName" now (in accordance to SQL Server provider).

Post Reply