I see lots of advocates suggesting that using SqlMembershipProvider is the way to go, and from the example code I've found I can see that it looks quite simple, once you have the provider set up, but I'm struggling with this step.
All the help and advice assumes that I have root access to the SQL server that will be used, or that the Express version is installed and everything will magiacally appear at first use, but I don't have that luxury, and I can't beleive I'm the only person trying to get the benefit of this expert code but doing it under shared hosting where I must create a specific SQL database and use my own credentials in my connection string.
I *think* I should be able to tell the SqlMembershipProvider to look at my web site's SQL Server database instead of going to its default SQLExpress or localhost instance, but how? and when I've done that, what tables, views and stored procedures will it expect to find in my data ...
Go to the complete details ...