如何将 IoC 成员资格提供程序与 ASP.NET MVC 集成

本文介绍了如何将 IoC 成员资格提供程序与 ASP.NET MVC 集成的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我有一个自定义成员资格/角色提供程序，我在我的 MVC 控制器中使用它，我也希望 ASP.NET MVC 可以访问它，因此我可以使用 AuthorizationFilters 等.由于很多人都实现了自定义提供程序，我想很多人们已经这样做了，但我还没有弄清楚或找到专门解决这个问题的帖子.这篇文章是我问题的另一面.就我而言，我的自定义提供程序与控制器配合良好，我也希望 MVC 使用它.

I have a custom membership/roles provider that I use in my MVC controllers that I also want to have accessible to ASP.NET MVC, so I can use AuthorizationFilters, etc. Since so many people have implemented custom providers I imagine many people have done this but I haven't figured it out or found postings that address this problem specifically. This post is sort of a flip side of my question. In my case I have my custom provider working well with my controllers, and I want MVC to use it too.

我的提供程序是通过 IoC/依赖项注入设计实现的.提供者公开了超出基线成员资格/角色 API 的附加功能.在我的控制器中，我使用 Castle Windsor 来创建实例.代码类似于:

My provider is implemented with a IoC/dependency injection design. The provider exposes additional functionality beyond the baseline membership/roles API. In my controllers, I use Castle Windsor to create instances. The code looks similar to:

public class HomeController : Controller { IMembershipService _membershipService; public HomeController(IMembershipService membershipService) { _membershipService= membershipService; } } <castle> <components> <component id="MembershipService" service="IMembershipService, MyApp" type="MembershipService, MyApp" lifestyle="PerWebRequest"> <parameters> <connectionString>#{defaultConnectionString}</connectionString> </parameters> </component> </components> </castle> public class WindsorControllerFactory : DefaultControllerFactory { private WindsorContainer _container; public WindsorControllerFactory() { _container = new WindsorContainer(new XmlInterpreter(new ConfigResource("castle"))); List<Type> controllerTypes = new List<Type>(); foreach (Type t in Assembly.GetExecutingAssembly().GetTypes()) { if (typeof(IController).IsAssignableFrom(t)) controllerTypes.Add(t); } foreach (Type t in controllerTypes) { // LifestyleType.Transient = new controller instance for each request _container.AddComponentLifeStyle(t.FullName, t, LifestyleType.Transient); } } protected override IController GetControllerInstance(Type controllerType) { return (IController)_container.Resolve(controllerType); }

这一切在我的 C# 代码中都很好用，但我想将我的提供者连接到 MVC 以使用 [Authorize] 过滤器:

This all works great in my C# code but I want to wire my provider into MVC to use [Authorize] filters with it:

[Authorize (Users="user1, user2", Roles="role8")] public ViewResult MyResult(int x) { // implement }

我知道告诉 ASP.NET 关于自定义成员资格或角色提供程序的常用方法是在 web.config 文件中，如下所示，但如果我这样做，ASP.NET 将尝试调用默认构造函数，它不会工作.任何帮助表示赞赏.

I know that the usual way to tell ASP.NET about a custom membership or roles provider is in the web.config file as below but if I do this ASP.NET will just try to call the default constructor, which won't work. Any help appreciated.

<membership> <providers> <clear/> <add name="MyMembershipProvider" type="MyMembershipProvider"> </providers> </membership>

推荐答案

最简单的方法是在 web.config 中使用 ASP.NET 的 标准机制.您只需让它使用默认构造函数但您覆盖 Initialize() 并拉那里的依赖项.使用这个作为参考.

The simplest way to get this to work is to use ASP.NET's standard mechanism of <membership> in web.config. You just let it use the default constructor but you override Initialize() and pull the dependencies there. Use this as reference.

就我个人而言，由于这样的事情，我更喜欢完全避免提供者模型，所以我使用了一种类似于 在 MonoRail 文档中描述.恕我直言，它不那么臃肿且更灵活.最后，它只是设置 HttpContext.User 具有适当的 IPrincipal 实现，它是AuthorizeAttribute 使用什么.

Personally, due to things like this, I prefer to avoid the provider model altogether so I use an approach similar to the ones described in the MonoRail docs. IMHO it's less bloated and more flexible. In the end, it's just about setting HttpContext.User with a proper IPrincipal implementation which is what the AuthorizeAttribute uses.

我最近写了一篇关于使用 MembershipProviders 进行适当 IoC 的解决方案的博客

I recently blogged about a solution to do proper IoC with MembershipProviders.