I am aware of the web parts control. But that may not fit what I need.
I am trying to extend the role model of ASP.NET. I read some chapters of a book and that is absolutly feasible.
But I am missing out something, hope someone could tell me where to look.
A Role will have a collection of principles (maybe I misunderstand it) and principles define what a role can or can not do.
I am using a MS SQL backend. Both RoleManager and Membership providers are using that Database.
My question is, I don't understand what a principle is, it didn't appears in the Database Schema.
And if I modify access rule in ASP.NET administration tool, it save a rule inside web.config.
What I am trying to do is to show controls depending on user role.
For example a menu or a treeview, different users will see different subset of items.
And that setting information will be store inside my database.
&nb ...
Go to the complete details ...