simple provider with mysql

Sep 17, 2012 at 7:59 AM

  I just created an mvc 4 application and added universal providers. I would like to customize the membership provider adding a custom provider that store the data in a mysql database.
  I created my provider and it works fine, but I have a problem.
  In the InitializeSimpleMembershipAttribute there is a call to

 WebSecurity.InitializeDatabaseConnection("DefaultConnection", "UserProfile", "UserId", "UserName", autoCreateTables: false);
  that must be done, even after i don't use it.

  If I remove this call, or the InitializeSimpleMembership in the controller the application doesn't work, but if I install this application in a server without Sql server doesn't work.
  If  I install this in a server with Sql server and MySql, this call is done doing nothing, and after this the procedure use correctly my custom membership provider.

  How can solve this problem and avoid the call to sqlserver?



  How can customize a memeber