This article was written for ASP.NET MVC 4 RC (Release Candidate). If you are still using Beta version of ASP.NET MVC 4 then you have to read the previous article.
HttpControllerFactory was deleted in ASP.NET MVC 4 RC. Actually, it was replaced by two interfaces: IHtttpControllerActivator and IHttpControllerSelector.
Unfortunately DefaultHttpControllerSelector still doesn't support Areas by default. To support it you have to write your HttpControllerSelector from scratch. To be honest, I will derive my selector from DefaultHttpControllerSelector.
In this post I will show you how you can do it.
First of all, you have to derive your class from DefaultHttpControllerSelector class:
public class AreaHttpControllerSelector : DefaultHttpControllerSelector { private readonly HttpConfiguration _configuration; public AreaHttpControllerSelector(HttpConfiguration configuration) : base(configuration) { _configuration = configuration; } }
In the constructor mentioned above I called the base constructor and stored the HttpConfiguration. We will use it a little bit later.
My code will use two constants:
private const string ControllerSuffix = "Controller"; private const string AreaRouteVariableName = "area";
You can understand why we need first one by name. The second one contains the name of the variable which we will use to specify area name in Routes collection.
Somewhere we have to store all of the API controllers.
private Dictionary<string, Type> _apiControllerTypes; private Dictionary<string, Type> ApiControllerTypes { get { return _apiControllerTypes ?? (_apiControllerTypes = GetControllerTypes()); } } private static Dictionary<string, Type> GetControllerTypes() { var assemblies = AppDomain.CurrentDomain.GetAssemblies(); var types = assemblies.SelectMany(a => a.GetTypes().Where(t => !t.IsAbstract && t.Name.EndsWith(ControllerSuffix) && typeof(IHttpController).IsAssignableFrom(t))) .ToDictionary(t => t.FullName, t => t); return types; }
Method GetControllerTypes takes all the API controllers types from all of your assemblies, and store it inside the dictionary, where the key is FullName of the type and value is the type itself.
Of course we will set this dictionary only once. And then just use it.
Now we are ready to implement one of the important method:
public override HttpControllerDescriptor SelectController(HttpRequestMessage request) { return GetApiController(request) ?? base.SelectController(request); }
In that method I try to take the HttpControllerDescriptor from method GetApiController and if it return null then call the base method.
And additional methods:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
|
Method GetAreaName just takes area name from HttpRequestMessage.
Method GetControllerTypeByArea are tries to find the controller in the ApiControllerTypes by full name of the controller where the full name contains area's name surrounded by "." (e.g. ".Admin.") and ends with controller name + controller suffix (e.g. UsersController).
And if a controller type found then method GetApiController will create and return back HttpControllerDescriptor.
So, my AreaHttpControllerSelector is ready to be registered in my application.
The next thing you have to do is to say to your application to use this controller selector instead of DefaultHttpControllerSelector. And fortunately it is really easy - just add one additional line to the end of Application_Start method in Glogal.asax file:
|
1 2 3 4 5 |
|
If you did everything right, now you can forget about that "nightmare" code mentioned above. And just start to use it!
You have to add new HttpRoute to your AreaRegistration.cs file:
|
1 2 3 4 5 6 7 8 9 10 |
|
Or just use one global route in your Global.asax like:
|
1 2 3 4 5 |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。