read uncommitted - Page 152

URL Routing in ASP.NET 4.0

In the .NET Framework 3.5 SP1, Microsoft introduced ASP.NET Routing, which decouples the URL of a resource from the physical file on the web server. With ASP.NET Routing you, the developer, define routing rules map route patterns to a class that generates the content. For example, you might indicate that the URL Categories/CategoryName maps to a class that takes the CategoryName and generates HTML that lists that category's products in a grid. With such a mapping, users could view products for the Beverages category by visiting www.yoursite.com/Categories/Beverages. In .NET 3.5 SP1, ASP.NET Routing was primarily designed for ASP.NET MVC applications, although as discussed in Using ASP.NET Routing Without ASP.NET MVC it is possible to implement ASP.NET Routing in a Web Forms application, as well. However, implementing ASP.NET Routing in a Web Forms application involves a bit of seemingly excessive legwork. In a Web Forms scenario we typically want to map a routing pattern to an actual ASP.NET page. To do so we need to create a route handler class that is invoked when the routing URL is requested and, in a sense, dispatches the request to the appropriate ASP.NET page. For instance, to map a route to a physical file, such as mapping Categories/CategoryName to ShowProductsByCategory.aspx - requires three steps: (1) Define the mapping in Global.asax, which maps a route pattern to a route handler class; (2) Create the route handler class, which is responsible for parsing the URL, storing any route parameters into some location that is accessible to the target page (such as HttpContext.Items), and returning an instance of the target page or HTTP Handler that handles the requested route; and (3) writing code in the target page to grab the route parameters and use them in rendering its content. Given how much effort it took to just read the preceding sentence (let alone write it) you can imagine that implementing ASP.NET Routing in a Web Forms application is not necessarily the most straightforward task. The good news is that ASP.NET 4.0 has greatly simplified ASP.NET Routing for Web Form applications by adding a number of classes and helper methods that can be used to encapsulate the aforementioned complexity. With ASP.NET 4.0 it's easier to define the routing rules and there's no need to create a custom route handling class. This article details these enhancements. Read on to learn more! Read More >

Search Results

Search found 30115 results on 1205 pages for 'read uncommitted'.

Page 152/1205 | < Previous Page | 148 149 150 151 152 153 154 155 156 157 158 159 | Next Page >

- by user1032531

- by Jialiang

- by stackuser

- by david.bain

- by Bill Evjen

- by KKline

- by Imran

- by Pinal Dave

- by jamiet

- by jamiet

- by Daniel Moth

- by nikolaosk

- by rickramsey

- by Daniel Cazzulino

- by JuergenKress

- by Jeffrey Sweeney

- by Marco Russo (SQLBI)

- by George Clingerman

- by jchang

- by Simon Cooper

- by pinaldave

- by bmdhacks

< Previous Page | 148 149 150 151 152 153 154 155 156 157 158 159 | Next Page >