Home/ Questions/Q 534857
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T09:39:22+00:00

We’re going to be using a custom role provider with WCF. The overridden method

  • 0

We’re going to be using a custom role provider with WCF. The overridden method GetRolesForUser will require the use of an already existing RoleRepository.

Now, with a run-of-the-mill class, we’d construct it using StructureMap and the RoleRepository dependency would be injected via the constructor.

However, it’s WCF that does the constructing of the the custom role provider class and that’s ‘done’ declaritavely via the roleManager attribute in the web.config.

I don’t really want to hard-wire the RoleRepository depndency into the custom role probvider class but it’s looking like I’ll have to.

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The RoleProvider and related types are legacies of ASP.NET which are infamous for not being DI-friendly. They require a default constructor and there are no hooks offered to initialize them. It sucks, but that’s the way it is.

    In such situations, the best remedy is to implement the RoleProvider as a Humble Object. In other words, the RoleProvider must wire up all dependencies, but from there, it delegates all implementation to your own open and extensible API.

    • 0