Articles : Page 1 of 1

  • Custom ASP.NET Routing to an HttpHandler

    Custom ASP.NET Routing to an HttpHandler

    Mar 11
    28

    As of version 4.0 ASP.NET natively supports routing via the now built-in System.Web.Routing namespace. Routing features are automatically integrated into the HtttpRuntime via a few custom interfaces. New Web Forms Routing Support In ASP.NET 4.0 there are a host of improvements including routing support baked into Web Forms via a RouteData property available on the Page class and RouteCollection.MapPageRoute() route handler that makes it easy to route to Web forms. To map ASP.NET Page rout...

  • Custom ASP.NET Routing to an HttpHandler

    Custom ASP.NET Routing to an HttpHandler

    Mar 11
    28

    As of version 4.0 ASP.NET natively supports routing via the now built-in System.Web.Routing namespace. Routing features are automatically integrated into the HtttpRuntime via a few custom interfaces. New Web Forms Routing Support In ASP.NET 4.0 there are a host of improvements including routing support baked into Web Forms via a RouteData property available on the Page class and RouteCollection.MapPageRoute() route handler that makes it easy to route to Web forms. To map ASP.NET Page rout...

  • Setting up custom ASP.NET Routing to an HttpHandler

    Setting up custom ASP.NET Routing to an HttpHandler

    Mar 11
    27

    As of version 4.0 ASP.NET natively supports routing via the now built-in System.Web.Routing namespace. Routing features are automatically integrated into the HtttpRuntime via a few custom interfaces. New Web Forms Routing Support In ASP.NET 4.0 there are a host of improvements including routing support baked into Web Forms via a RouteData property available on the Page class and RouteCollection.MapPageRoute() route handler that makes it easy to route to Web forms. To map ASP.NET Page rout...

  • Integrating ASP.NET MVC 3 into existing upgraded ASP.NET 4 Web Forms applications

    Integrating ASP.NET MVC 3 into existing upgraded ASP.NET 4 Web Forms applications

    Jan 11
    06

    I got an interesting question recently from a gentleman who has an existing ASP.NET WebForms 2.0 application that works just fine. He's upgraded it to ASP.NET 4 and it still works great, but now he wants to add some ASP.NET MVC pages to it. He doesn't want to rewrite the application. A few years ago I did a post on Hybrid ASP.NET applications. The goal was to reinforce the point that you can have ASP.NET applications that are both WebForms and MVC (as well as WCF and ASMX Web Services and o...

  • Named Routes To The Rescue

    Named Routes To The Rescue

    Nov 10
    22

    The beginning of wisdom is to call things by their right names – Chinese Proverb Routing in ASP.NET doesn’t require that you name your routes, and in many cases it works out great. When you want to generate an URL, you grab this bag of values you have lying around, hand it to the routing engine, and let it sort it all out. For example, suppose an application has the following two routes define routes.MapRoute( name: "Test", url: "code/p/{action}/{id}", defaults: new { controller = "Se...

  • 1