I’ve tried to enable custom errors on production server for 3 hours, seems I found final solution how to do this in ASP.NET MVC without any routes. To enable custom errors in ASP.NET MVC application we need (IIS 7+): Configure custom pages in web config under system.web section: <customErrors mode=”RemoteOnly” defaultRedirect=”~/error”> <error statusCode=”404″ redirect=”~/error/Error404″ /> … Read more
MVC doesn’t support method overloading based solely on signature, so this will fail: public ActionResult MyMethod(int someInt) { /* … */ } public ActionResult MyMethod(string someString) { /* … */ } However, it does support method overloading based on attribute: [RequireRequestValue(“someInt”)] public ActionResult MyMethod(int someInt) { /* … */ } [RequireRequestValue(“someString”)] public ActionResult MyMethod(string someString) … Read more
If you do it at the end of Application_Start it will be too late, as WebApiConfig.Register has been called. The best way to resolve this is to use new initialization method by replacing in Global.asax : WebApiConfig.Register(GlobalConfiguration.Configuration); by GlobalConfiguration.Configure(WebApiConfig.Register);
You can do it by creating a new route and adding it to the routes collection in RegisterRoutes in your global.asax. Below is a very simple example of a custom Route: public class ExampleRoute : RouteBase { public override RouteData GetRouteData(HttpContextBase httpContext) { var url = httpContext.Request.Headers[“HOST”]; var index = url.IndexOf(“.”); if (index < 0) … Read more