title: Identical route working in RouteConfig, but not AreaRegistration
body: <p>I am working in a Web Site Project (not Web Application) where Web Forms and MVC happily live together.  To organize my code, I'm trying to setup Areas with the MVC part and am running into this situation.</p>
  
  <p>I've setup my area with my controllers and I create the following area configuration:</p>
  
  <pre><code>Namespace Areas.Awesome
  
      Public Class AwesomeAreaRegistration
          Inherits AreaRegistration
  
          Public Overrides ReadOnly Property AreaName As String
              Get
                  Return "Awesome"
              End Get
          End Property
  
          Public Overrides Sub RegisterArea(context As AreaRegistrationContext)
  
              context.MapRoute(
                  "Awesome_default",
                  "Awesome/{controller}/{action}/{id}",
                  New With {.controller = "Sauce", .action = "Index", .id = UrlParameter.Optional},
                  New String() {"Areas.Awesome"}
              )
  
          End Sub
  
      End Class
  
  End Namespace
  </code></pre>
  
  <p>When I try to navigate to <code>/Awesome/Sauce/</code> I get a 404 error and my site actually tries to route me to <code>/Awesome/Sauce/Default.aspx</code>.</p>
  
  <p>HOWEVER, when I move the route to my <code>RouteConfig</code>:</p>
  
  <pre><code>Public Module RouteConfig
  
      Public Sub RegisterRoutes(ByVal routes As RouteCollection)
          routes.IgnoreRoute("{resource}.axd/{*pathInfo}")
          routes.IgnoreRoute("{resource}.aspx/{*pathInfo}")
  
          routes.MapRoute(
              "Awesome_default",
              "Awesome/{controller}/{action}/{id}",
              New With {.controller = "Sauce", .action = "Index", .id = UrlParameter.Optional},
              New String() {"Areas.Awesome"}
          )
      End Sub
  
  End Module
  </code></pre>
  
  <p>This serves  up <code>/Awesome/Sauce/</code> as expected.  </p>
  
  <p>I did some digging and created both routes at the same time, but with different URIs and I found they were both being defined in the same way, but one was working and one was not.</p>
  
  <p>Is there something I'm missing with the area registration that would cause these routes to be ignored while the ones defined in RouteConfig are not?</p>