Apr 30, 2012 03:46 PM|XIII|LINK
Wen Hao Mui
there is no longer requiring using Aspnetdb.mdf anymore
Why not? Of course if that's the place where your RoleProvider, by default, looks for the roles associtated with the users. What I suggested was to add the roles to the database via the provider in the Application_Start if they're not yet there.
Make use of the
If you don't want to have two databases then there's a good way to have the aspnetdb.mdf database integrated into your own:
Create Membership tables in another database than the standard aspnetdb.mdf.