title: Routing is finding the controller in my areas, but not the views
body: <p>I'm trying to use Maarten Balliauw's <a href="http://blog.maartenballiauw.be/post/2009/05/20/ASPNET-MVC-Domain-Routing.aspx" rel="noreferrer">Domain Route</a> class to map sub-domains to the areas in an MVC2 app so that I have URLs like:</p>
  
  <pre><code>http://admin.mydomain.com/home/index
  </code></pre>
  
  <p>instead of:</p>
  
  <pre><code>http://mydomain.com/admin/home/index
  </code></pre>
  
  <p>So far, I've only had partial success. Execution is being routed to the correct controller in the correct area, but it cannot then find the correct view. I'm receiving the following error:</p>
  
  <pre><code>The view 'Index' or its master was not found. The following locations were searched:
  ~/Views/AdminHome/Index.aspx
  ~/Views/AdminHome/Index.ascx
  ~/Views/Shared/Index.aspx
  ~/Views/Shared/Index.ascx 
  </code></pre>
  
  <p>This indicates to me that MVC is looking for the view only in the root views folder and not the views folder within the Area. If I copy the view from the Area's views folder to the root views folder, the page renders fine. This however, completely defeats the purpose of dividing the APP into Areas.</p>
  
  <p>I'm defining the route for the area as:</p>
  
  <pre><code>public class AdminAreaRegistration : AreaRegistration
  {
      public override string AreaName
      {
          get { return "Admin"; }
      }
  
      public override void RegisterArea(AreaRegistrationContext context)
      {
          context.Routes.Add(
              "Admin_Default"
              , new DomainRoute(
                  "admin.localhost"
                  , "{controller}/{action}/{id}"
                  , new { controller = "AdminHome", action = "Index", id = UrlParameter.Optional }
          ));
      }
  }
  </code></pre>
  
  <p>I'm confused as to why it is finding the controller within the Area fine, but not the view.</p>