I want some links to include a fragment identifier. Like some of the URLs on this site:

Is there a way to do this with any of the builtin methods in MVC? Or would I have to roll my own HTML helpers?


+2  A: 

The short answer is: No. In ASP.NET MVC Preview 3 there's no first-class way for including an anchor in an action link. Unlike Rails' url_for :anchor, UrlHelper.GenerateUrl (and ActionLink, RedirectToAction and so on which use it) don't have a magic property name that lets you encode an anchor.

As you point out, you could roll your own that does. This is probably the cleanest solution.

Hackily, you could just include an anchor in a route and specify the value in your parameters hash:

routes.MapRoute("WithTarget", "{controller}/{action}/{id}#{target}");
<%= Html.ActionLink("Home", "Index", new { target = "foo" })%>

This will generate a URL like /Home/Index/#foo. Unfortunately this doesn't play well with URL parameters, which appear at the end of the URL. So this hack is only workable in really simple circumstances where all of your parameters appear as URL path components.

Dominic Cooney
+5  A: 

We're looking at including support for this in our next release.

is this going to be targetting to be released in the dev10?
+3  A: 


I'm almost positive that putting that in the route will cause routing issues.


Until MVC has support for this, you can be a little more "old school" about how you make your routes. For example, you can convert:

<%= Html.ActionLink("Home", "Index") %>


<a href='<%= Url.Action("Index") %>#2345'>Home</a>

Or you can write your own helper that does essentially the same thing.

Brad Wilson
I tried targets in routes with ASP.NET MVC Preview 3 and there was no problem with routing. So although you're "almost positive" it would be useful for you to elaborate on what issues there will be.
Dominic Cooney
+2  A: 

As Brad Wilson wrote, you can build your own link in your views by simply concatenating strings. But to append a fragment name to a redirect generated via RedirectToAction (or similar) you'll need something like this:

public class RedirectToRouteResultEx : RedirectToRouteResult {

    public RedirectToRouteResultEx(RouteValueDictionary values)
        : base(values) {

    public RedirectToRouteResultEx(string routeName, RouteValueDictionary values)
        : base(routeName, values) {

    public override void ExecuteResult(ControllerContext context) {
        var destination = new StringBuilder();

        var helper = new UrlHelper(context.RequestContext);
        destination.Append(helper.RouteUrl(RouteName, RouteValues));

        //Add href fragment if set
        if (!string.IsNullOrEmpty(Fragment)) {
            destination.AppendFormat("#{0}", Fragment);

        context.HttpContext.Response.Redirect(destination.ToString(), false);

    public string Fragment { get; set; }

public static class RedirectToRouteResultExtensions {
    public static RedirectToRouteResultEx AddFragment(this RedirectToRouteResult result, string fragment) {
        return new RedirectToRouteResultEx(result.RouteName, result.RouteValues) {
            Fragment = fragment

And then, in your controller, you'd call:

return RedirectToAction("MyAction", "MyController")

That should generate the URL correctly.