We are going to implement all three of our core end-user
browsing experiences using a single controller class - which we'll call
"ProductsController" (right click on the "Controllers" sub
folder and select "Add New Item" -> "MVC Controller" in
order to create it:
Figure 6
Our ProductsController class will handle URLs
like /Products/Category/3, /Products/New, and /Products/Edit/5 by implementing
"Category", "New", and "Edit" actions:
Figure 7
Read Part 1 and Part 2 of my ASP.NET MVC Series to learn more about how
these URLs are routed to the action methods on the ProductsController
class. For this sample we are going to use the default
/[Controller]/[Action]/[Id] route mapping rule - which means we do not need to
configure anything in order for the routing to happen.
Our Controller actions will be using three View pages in
order to render output. The "List.aspx", "New.aspx",
and "Edit.aspx" pages will live under the \Views\Products sub-folder,
and be based on the Site.Master master page under \Views\Shared.
