I suggest you ...

Make SecUtility and other utility classes public rather than internal sealed

I'm trying to build my own role provider for ASP.NET that supports nested hierarchies for roles - like Active Directory, but SQL-based (as an LDAP server is somewhat overkill for my needs, and yes I've seen the new stuff about Windows Azure AD services).

Having reflected (using ILSpy) the deault SqlRoleProvider to keep my code almost identical, I find that most of the classes utilised in there, such as System.Web.Util.SecUtility for parameter checking, System.Web.DataAccess.SqlConnectionHolder for attaching a SQL connection to an HttpContext for application re-use, and System.Web.SR for string resources, are all marked as internal (and in some instances sealed), and therefore cannot be accessed by third-party libraries.

Please can you make these classes public and virtual, as they're kinda useful, and I'd like to be able to use the utilities in the above described classes, and over-ride them with my own implementations in some instances.

4 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Benjamin HowarthBenjamin Howarth shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base