Dependency injection and ASP.Net Membership Providers

Question

I am in the process of creating a custom membership provider for an ASP.Net MVC website. The provider is being created as a separate class as part of a bigger library. There

Answer 1

Isn't this better? I use it with MVC3 and ninject. It's enough to add a property to your custom membership provider class. Remember to add "using System.Web.Mvc;" on top.

public IRepository Repository
{
    get
    {
        return DependencyResolver.Current.GetService();
    }
}