How to implement a mechanism (within a single ASP.NET MVC application) to ensure that:
- if request comes on mydomain (user visits mydomain.com) -> handle using certain set of controllers
- if request comes on otherdomain (user visits otherdomain.com) -> handle using different set of controllers
(the domains are aliased to the same web hosting)
What extension points within ASP.NET MVC should I use to ensure that the described mechanism works?
I think you could implement a
IRouteConstraintdescendant that analyzes the currentHttpContextand matches (or does not match) a route depending on the domain requested. Then have two different default routes in your Global.asax file, each with different constraints.I would still prefer two applications, but it’s your choice of course.