Before ASP.NET MVC, the core assumption of routing in ASP.NET (just like in many other web application platforms) was that URLs correspond directly to files on the server's hard disk. The server executes and serves the page or file corresponding to the incoming URL. Table 8-1 gives an example.
Table 8-1. How URLs Have Traditionally Corresponded to Files on Disk
Might Correspond To
File not found! Send error 404.
This strictly enforced correspondence is easy to understand, but it's also very limiting. Why should my project's file names and directory structure ...