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.
XIII
All-Star
182684 Points
23455 Posts
ASPInsiders
Moderator
MVP
Re: Managing website using role
Apr 30, 2012 02:46 PM|LINK
Hi,
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 Roles.RoleExists and Roles.CreateRole methods.
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.
Grz, Kris.
Interested in Azure, ASP.NET (MVC), jQuery, WCF, EF, MS SQL, ...
Keep the forums clean: report to the moderation team!