When I wrote the first post in this series, there was tremendous amount of interest generated and also a lot of feedback requesting to post some of the advanced features. Like I said earlier, ASP.NET 4.0 has lots of new features some of them as simple as Page.Title whereas so as big as caching improvements. This post covers one such feature which is Routing in Webforms. Although Routing was available even in .NET 3.5 SP1, (check this excellent post by Phil Haack on implementing Routing in ASP.NET 3.5 with .NET 3.5 SP1), it was kind of less known. Also the plumbing work was too much for getting it implemented. However, this has been much simplified in ASP.NET 4.0. To give a background, System.Web.Routing is the namespace that provides the all important RouteTable & PageRouteHandler class. Initially System.Web.Routing was an integral part of ASP.NET MVC. However, the team must have anticipated that Routing is more important even for Webforms and hence they moved this DLL outside the scope of just MVC and made it available to Webforms as well. Importance of Routing : Getting friendlier URLs which help in better search engine optimization and indexing. Cleaner URLs that can be bookmarked than the unfriendly querystring based approach. As more and more URLs are available, the chances of improvement in search engine ranking becomes higher. These are some of the general advantages of Routing and friendly URLs. Ok, now that the context is established, lets start with our sample. To begin with, I am using Visual Studio 2010 Beta 1 ( download link ) and Northwind Sample Database ( download link ) I created a “File – New Project – ASP.NET Web Application†leaving the default .NET 4.0 as the framework option

See the article here:
What’s new in ASP.NET 4.0 – Part II – Routing in Webforms