asp.net-mvc-routing

I'm working with some third-party software that creates querystring parameters with hyphens in their names. I was taking a look at this SO question and it seems like their solution is very close to what I need but I'm too ignorant to the underlying MVC stuff to figure out how to adapt this to do what I need. Ideally, I'd like to simply replace hyphens with underscores and that would be a good enough solution. If there's a better one, then I'm interested in hearing it. An example of a URL I want to handle is this: http://localhost/app/Person/List?First-Name=Bob&My-Age=3 with this Controller:

I'm fairly new to MVC and am struggling with routing when I try to pass multiple parameters via the URL. From a page with the URL: /PersonCAFDetail/Index/3?memberid=4 ...I'm trying to get an Html.ActionLink set to point to the Create action such that the id=3 and the memberid=4. Having read a number of similar posts it seems that the following should work: @Html.ActionLink("Create New", "Create", null, new { memberid = "memberid" }) However, this results in a URL being created as follows: <a href="/PersonCAFDetail/Create/3" memberid="memberid">Create New</a> I have a route set up as: routes

We're considering moving forward with a ASP.NET MVC project and the subject of routing versus parameters came up. Seeing as how you can easily set up either or a combination of both in ASP.NET MVC, are there any considerations that I should be aware of when using one or the other? amurra I would recommend keeping your URL's as clean as possible and to try and use routes whenever possible. You should try and make RESTful URI's that will convey information to the user. For example: www.yourdomain.com/Products/Sports/Clothing is a lot cleaner than www.yourdomain.com/Products?Department=Sports

A new .net core web application project comes with the following route configuration: app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); If you replace this with app.UseMvc() and add appropriate Route attributes for both HomeController and its actions (Index, About, Contact, Error), it would still work. Since we're not specifying a default route, the default view (Home/Index) will not be rendered if you hit http://localhost:25137/ . Hope that understanding is correct! Now, since I need the default view to be shown when the http:/

I'm working on a site that is partially static content and partially MVC. The root of the site is index.html and I have all of the controllers explicitly routed and all html files ignored. However, when you hit the root of the website, it tries to route it. How can I tell the route engine to ignore the root of the site? www.mysite.com should not be routed, but instead go to index.html. Here is my routing configuration: routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.IgnoreRoute("*.html|js|css|gif|jpg|jpeg|png|swf"); routes.MapRoute( "vendor_signup","{vendor}/signup/{action}/", new {

I've seen both being used and so I wonder, do they do the same thing or different things? If it's the latter, what's the difference? I tried answering it myself by having a look at the visual studio MVC 4 (rc) web api template, but sadly it uses both, so my confusion remains. Here's what the template contains: public class RouteConfig { public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapHttpRoute( name: "DefaultApi", routeTemplate: "api/{controller}/{id}", defaults: new { id = RouteParameter.Optional } ); routes.MapRoute(