ASP.NET MVC2 Routing IIS6 - only default routes work

Question

I've deployed an ASP.NET MVC2 website on a Windows Server 2003 machine running IIS 6. I'm using pretty much the default routing in a standard MVC project:

public static void RegisterRoutes(RouteCollection routes)
    {
        routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

        routes.MapRoute(
            "Default", // Route name
            "{controller}/{action}/{id}", // URL with parameters
            new { controller = "Products", action = "List", id = UrlParameter.Optional } // Parameter defaults
        );

    }

Navigating to http://localhost/MyApplication takes me to the List page just fine. Navigating to http://localhost/MyApplication/Products/Details/21 gives me a 404. This routing worked fine on the inbuilt development server in VS2010.

I've put in the standard IIS wildcard aspnet_isapi.dll mapping mentioned all over the place - navigating to the List page didn't work before I did - but navigating to anything other than the default route is broken.

I'd really like to keep my extensionless URLs. Does anyone have any idea as to why the routing would work for the default webpage, but no others?

*Edit: just tried adding the .aspx extension, ie now my route looks like this:

        routes.MapRoute(
            "Default", // Route name
            "{controller}.aspx/{action}/{id}", // URL with parameters
            new { controller = "Downtime", action = "List", id = UrlParameter.Optional } // Parameter defaults
        );

And it has the same behaviour, except this time I get the asp 404 page instead of the html 404 page...

*Edit 2: tried it again using the following route and making sure .mvc was mapped to aspnet_isapi.dll:

        routes.MapRoute(
            "Default", // Route name
            "{controller}.mvc/{action}/{id}", // URL with parameters
            new { controller = "Downtime", action = "List", id = UrlParameter.Optional } // Parameter defaults
        );

This time I got an 'Internet Explorer cannot display the webpage' 404-style page. I've now got 3 different 404 errors from using these 3 different methods...

*Edit 3 Return of the Edit: I have the site running in IIS 5.1 on Windows XP professional with only a wildcard remapping on the virtual directory, but heaven forbid I can get it to run on the webserver...

Answer 1

Found it - the routing is actually working, my URLs were not. I was using javascript to build some of the URLs and it turns out that I wasn't linking to

http: //localhost/MyApplication/Controller/Action/ID

I was actually linking to

http: //localhost/Controller/Action/ID

Building the links like this was working on the development server, but once the site was deployed to a virtual directory on the webserver those addresses are incorrect because of the extra application name in the URL.

In conclusion, be careful with your URLs - don't build them out of strings like I did.