Fairly new to ASP, and I have created a custom security database using aspnet_regsql. I created the custom SQLMEMBERSHIPPROVIDER in web.config and told the web admin tool that I want to use this provider. The test connection was fine. I added the custom membership provider to the Login control, create user account control etc. in properties.
When I added a user for the first time, the ASPNETDB.MDF was created in App_data, AND the user was added to both my custom SQL Server 2008 security database AND the ASPNETDB.MDF.
In the ASPNETDB.MDF the aspnet_Membership table is empty. In the custom database the membership table has the user added. Both databases contain the aspnet_Users data and if I add a new user the new user is added to both databases.
Is this the way it is supposed to work?
In this scenario do I need to publish the ASPNETDB.MDF?
What is the advantage to having a custom database? I still ...
Go to the complete details ...