ScottGu forwarded me an email from a developer this weekend who wanted to use ASP.NET Membership in an application deployed on a shared hosting account that allows only one SQL Server database.
It’s not all that difficult to add ASP.NET membership (as well as other ASP.NET services) to your existing database.
ASP.NET doesn’t really care where the information repository for it’s built in services live as long as they are complete.
The database that contains the ASP.NET Application Services repository is resolved via a standard connection string in the application’s web.config file.
1: <connectionStrings>
2: <add name="Applicat ...
Go to the complete details ...