Oct 23, 2011 at 1:39 AM
Edited Oct 23, 2011 at 3:32 AM
A quick update for anyone following this:
I have AzureProviders Membership provider working against SQL Express on my dev enviro, very easy with just a change the web.config:
replace this: name="AzureMembershipProvider"
Next, replace the custom profile and
role providers with the default ASP.NET providers (see web.config of a new ASP.NET project that uses Membership). Be sure also to add these properties inside the <profile> section since AzureProviders
Now make sure a connection string to the memberhsip DB is of course added and correct, as follows:
connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=ASPNETMembership;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />
I am looking at using SQL Azure JUST for Membership, but use ATS for everything else (sessions, etc) in AzureProviders. This would be useful because I have other software that I use to administer
the membership data that points to the same SQL membership data store.
Note that on Azure, you must use the updated scripts in order for ASP.NET Membership to work on SQL Azure (see
here or here).