1 comment

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• AdminDaniel Roth (Admin, ASP.NET Future Feature Feedback) commented  ·  November 15, 2012 4:40 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Looking at your blog post I believe you highlight four issues:

  1. Why do you need to specify a route name to generate a link when the MVC UrlHelper.Action(…) method don’t require you to specify one?
  - Looks like the behavior of MVC is to iterate over the routes and pick the first one that happens to work. Is this the desired behavior?
  2. Cannot foreach loop over HttpRouteCollection
  - Fixed!
  3. No way to get the name of a route from the route or the route collection
  - This is really an issue with ASP.NET Routing, although it is aggravated by Web API requiring the route name to generate links.
  4. Creating a Web API UrlHelper should only require the request, not the controller context
  - Fixed! You can create a UrlHelper with just the request.