text: Q:
  
  When deploying an ASP.MVC 3 application to a subfolder (not root), how do I handle routes?
  
  I'm developing an ASP.MVC 3 project on my local computer where it is located at the root of the local web server. 
  localhost:12345/(project is here)
  
  However, when I deploy to our public web server this application will be located in a subfolder
  www.mycompany.com/myapp/(project goes here)
  
  How do I deal with that mismatch? A few questions come to mind:
  
  Do I need to adjust my MVC routes? Or will they just capture anything after /myapp/ ?
  Do I use HomeController when I don't really want 'Home' to appear in the route? i.e. /myapp/home/(action)/(id) - rather I want this: /myapp/(action)/(id) if Home is the controller.
  Should I match this folder structure on my local machine? (This project will never have access to anything outside that 'myapp' folder)
  If 3 is yes, how?
  
  I'm using VS 2010 with IIS Express locally.
  
  A:
  
  The routes are relative to the web application. Which means that you don't need to have /myapp/ in your routes.
  No you don't need to have Home appear in the route. Personally as a practice I take out the default route.
  No you don't need to match this folder structure.
  
  