Ok, I'm in a bit of a pickle. Backstory: I'm only vaguely familiar with ASP.NET (C#) - I'm primarily a Java guy. Anyhow, my company got a project to redevelop a web app and as always we're short handed. The customer has a database and compiled code, but no source. They have plenty of complaints so we're going to redevelop the app. The database looks good to me - and after a couple months worth of requirements analysis, there are only a couple minor things I'd change.
My problem is with .Net's membership provider. Am I missing something or does the model not provide for permissions? It looks like it ends with roles. My customer requires the ability to create new roles as needed. I was thinking to have permanent permissions defined and associated with roles for user management convenience, but the apps features are to be controlled by whether the user has a given permission or ...
Go to the complete details ...