ASP. NET WebForms 4.0 supports one-way routing (MVC)

The ASP. NET Routing engine was added in. NET Framework 3.5 SP1. Now
Microsoft have added better support for using the engine in ASP. NET
WebForms 4.0 by using expression builders enabling bi-directional
Routing.

Channel9 have just published a new episode of 10-4 showing how to use this new functionality in ASP. NET 4.0. in the video Jonathan Carter walk through a simple example of how to enable this in an existing ASP. NET application.

Below is a summary of the code showed in the video. They use
Typical example of how Product. aspx? Category = jerseys can map
Product/Jerseys. Using the ASP. NET Routing engine this mapping can be
Added using the RouteTable in Application_Start:

RouteTable.Routes.Add("Product", 
                      new Route("Product/{name}", 
                      new PageRouteHandler("~/Product.aspx")));

To add bi-directional routing support today, users wowould have to use URL rewriting on the query string. However, in ASP. NET 4.0 users can register expression builders:

<system.web>
  <compilation>
    <expressionBuilders ...>
      <add expressionPrefix="RouteUrl" 
           type="System.Web.Compilation.RouteUrlExpressionBuilder" />

      <add expressionPrefix="RouteValue"
           type="System.Web.Compilation.RouteValueExpressionBuilder" />
    </expressionBuilders>
  </compilation>
</system.web>

The first expression is for getting a URL and the second for getting
A value. The $ sign is used to access expressions from an aspx page:

<asp:HyperLink NavigationUrl="<%$ RouteUrl:RouteName=Product, name=Jerseys" 
     Text="Jerseys" 
     runat="server" />

To get the value from the name attribute, users use the Route object instead of the Request object:

RouteData.Values["name"];

Or using an expression builder:

<%$ RouteValue:name %>

By using ASP. NET Routing and the new bi-directional support users
Can decouple URLs from a physical Web Form, allowing friendlier URLs
And have search engines discover and use these.