Good question. Mvc will support any path you thorw at it as long as it's pattern is mapped in the route dictionary. For example in my case I have such a big Mvc app I decided to create sub-folders for my controllers. Remember, the Mvc routingengine abstracts the folder structure you have so you don't have to reveal your folder structure in your url. I have an Account folder with an AccountController, AccountSummaryController, etc. So my url would look like /Account/Account/GetMyDataById/101, but it doesn't, it only shows /Account/GetMyDataById/101.
If you do not specifcy the “/” in front of the Account in your url in your ajax call, the routing engine will prefix your url with the current url, so you will get something like /Account/GetMyDataById/Account/GetMyDataById/101. So make sure you prefix url with an “/” and include the controller: “/Account/GetMyDataById“.
Just as an example my route map looks like this:
routes.MapRoute(“Account”, “Account/{action}/{accountId}”,
.
