Try something like this: routes.IgnoreRoute(“{resource}.axd/{*pathInfo}”); routes.MapRoute( “OnlyAction”, “{action}”, new { controller = “Home”, action = “Index” } ); routes.MapRoute( “Default”, // Route name “{controller}/{action}/{id}”, // URL with parameters new { controller = “Home”, action = “Index”, id = UrlParameter.Optional } // Parameter defaults );
You could add the following handler to the <handlers> section of your <system.webServer>: <add name=”ManagedDllExtension” path=”api/nav/*/*.dll” verb=”GET” type=”System.Web.Handlers.TransferRequestHandler” preCondition=”integratedMode,runtimeVersionv4.0″ /> This will make all requests containing .dll be served through the managed pipeline. Also notice how I have limited them only to the GET verb to limit the performance impact.
You cannot include the query string in the route. Try with a route like this: routes.MapRoute(“OpenCase”, “ABC/ABC{stepNo}”, new { controller = “ABC1”, action = “OpenCase” }); Then, on your controller add a method like this: public class ABC1 : Controller { public ActionResult OpenCase(string stepno, string key, string group) { // do stuff here return … Read more
You mean like using the Action method on the Url helper: <%= Url.Action(“DoThis”, “MyController”) %> or in Razor: @Url.Action(“DoThis”, “MyController”) which will give you a relative url (/MyController/DoThis). And if you wanted to get an absolute url (http://localhost:8385/MyController/DoThis): <%= Url.Action(“DoThis”, “MyController”, null, Request.Url.Scheme, null) %>
Simply specify a blank area for them if they are to be served from root controllers: <li>@Html.ActionLink(“About Us”, “About”, “Home”, new { area = “” }, null)</li>
There are two steps to solve this problem. First, create a new route or change the default route to accept an additional parameter: routes.MapRoute( “Default”, // Route name “{controller}/{action}/{id}/{ignoreThisBit}”, new { controller = “Home”, action = “Index”, id = “”, ignoreThisBit = “”} // Parameter defaults ) Now you can type whatever you want to … Read more
if you don’t want to use RedirectToAction (for me is the right choice) you can use return Redirect(Url.Content(“~/”)); UPDATE As stated in the comments, this should also works return Redirect(“~/”);
Create a RouteConstraint like the following: public class GuidConstraint : IRouteConstraint { public bool Match(HttpContextBase httpContext, Route route, string parameterName, RouteValueDictionary values, RouteDirection routeDirection) { if (values.ContainsKey(parameterName)) { string stringValue = values[parameterName] as string; if (!string.IsNullOrEmpty(stringValue)) { Guid guidValue; return Guid.TryParse(stringValue, out guidValue) && (guidValue != Guid.Empty); } } return false; }} Next when adding … Read more
It’s not impossible as I have just recently found out. It’s actually added into the Items property of the current HttpContext (if there is one) =[ HttpRequestMessage httpRequestMessage = HttpContext.Current.Items[“MS_HttpRequestMessage”] as HttpRequestMessage Edit: This is as of WebAPI v2 .. I cannot be sure of previous versions.
When using forms authentication and the user is not authenticated or authorized the ASP.NET security pipeline will redirect to the login page and pass as a parameter in the query string the returnUrl equal to the page that redirected to the login page. The login action grabs the value of this parameter and puts it … Read more