10-4 Episode 11: Bi-Directional Routing with ASP.NET WebForms 4.0 (Channel 9)

10-4 Episode 11: Bi-Directional Routing with ASP.NET WebForms 4.0

Posted: Mar 04, 2009 at 8:30 PM

By: Jonathan Carter

(4)

60,012 Views

10 Comments

19 minutes, 24 seconds

Download

Right click “Save as…”

High Quality WMV (PC, Xbox, MCE)
MP3 (Audio only)
MP4 (iPod, Zune HD)
Mid Quality WMV (Lo-band, Mobile)

format
< > embed
+ queue

Sign In first to access your queue.
Close

Sorry, video was not added to the queue, an error occurred. Please Contact Us and let us know.
Close

Embed code for this video

Copy the code above to embed our video on your website/blog.

Video format

Auto
Use our suggested format for this video.
Smooth Streaming
Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth.
Progressive
Traditional buffered video format.
HTML5
For browsers that support h264 MP4 or WebM video playback such as:
IE9+, Chrome 5+, or Safari 4+.

Note: These selections will fall back to the next best format depending upon browser capability.

In this episode of 10-4, we introduce another new feature of ASP.NET WebForms 4.0: Routing. The ASP.NET Routing engine was added in the .NET Framework 3.5 SP1 release and is heavily leveraged by both ASP.NET MVC and ASP.NET Dynamic Data to provide bi-directional routing functionality. With the release of ASP.NET WebForms 4.0, you can take full advantage of the common route engine that allows you to customize the URLs that your application exposes. In addition, new expression builders allow you to generate dynamic URLs that are based on your route definitions, alleviating you from having to hard code static links.

For more 10-4 episodes, be sure to visit:
http://channel9.msdn.com/shows/10-4

Visual Studio Topic Area on Channel 9:
http://channel9.msdn.com/VisualStudio

Visual Studio 2010 CTP VPC:
http://tinyurl.com/GetCTP

ASP.NET Routing:
http://msdn.microsoft.com/en-us/library/cc668201.aspx

10-4! Over and out!

I would go with the unique string approach. Since part of the whole objective is to provide more meaningful URLs to end users, integer/guid identifiers don't really provide them any value. That doesn't mean that you won't still need to do something along the lines of "Products/1" in situations were that makes sense. You might have resources that don't legitimately have a unique value other than an ID. For SEO purposes having a descriptive value in the URL certainly helps as well. "Products/Cups" is capable of being spidered as a resource on "cups" whereas "Products/45" isn't. Will that make a huge difference? Maybe not, but every little bit helps Smiley

There is no need to get religious on either approach, it all just comes down to which approach serves the needs of your application the best. Since routing is so extensible, you should have fun building the sitemap you want. There is soooo much more to it then what I showed in this demo since this episode was meant only to show how routing and webforms can work together. General purpose routing has plenty of awesome little features.

I doubt there will be a 10-4 episode on ASP.NET Routing specifically since it isn't a feature in .NET Framework 4.0, but I could throw together some ad-hoc screencasts and plop them on my blog (http://www.lostintangent.com) or C9.

Keep these great questions coming guys, I seriously love the 10-4 community Smiley

Follow the Discussion

Subscribe to these comments

Ivannicoff Ivannicoff

Mar 05, 2009 at 5:07 AM quote reply

That is great! Will it be possible to have declarative syntax of it? For example in web.routing file?
JC can you tell about changes of App_Theme? I wrote about it on connect but no answer.
Ivannicoff Ivannicoff

Mar 05, 2009 at 5:08 AM quote reply

And about new rendering mode of controls.
Thank you.
MatKozlow

Mar 05, 2009 at 12:09 PM quote reply

Very well implemented very useful feature!
One question: what about urls localization?
Should I populate the RouteTable by hand for every languages or there is some resource related stuffs in the API?
Thx
LostInTangent

Mar 05, 2009 at 1:32 PM quote reply

That is one of the first questions that always comes up after seeing ASP.NET Routing As of right now the only way to configure your routes is through code. That said, I'm a firm believer that a good API is the perfect foundation for layering additional forms of expression (i.e. loading routes from a config file or DB). There are a couple prototypes floating around that pull your route definitions from config that I'd be more than happy to share with you.

As far as new rendering of controls, I'll deifnitely try to fit this in later episodes. Funny enough I actually showed off a very subtle change to the ListView control in this episode but I didn't call it out. You no longer have to have a PlaceHolderTemplate if your ItemTemplate's contents are truly seperate markup (i.e. not <li>'s within a <ul> for instance).

Feel free to email me (joncart at microsoft dot com) and I can share some additional info in the meantine.
Ivannicoff Ivannicoff

Mar 05, 2009 at 3:03 PM quote reply

Thank you JC! I wrote you some ideas a month ago.
JoshBlack

Mar 05, 2009 at 4:20 PM quote reply

Do the new route tools help in moving from a site with identity keys (int) to text values.

products.aspx?pid=1
becomes
products/chairs/

I guess it would be difficult to map all the number / string pairs as routes in a config file. I assume they could be added programatically on application start. They would have to be recreated if something was later added to the database?

Or do you suggest moving away from passing the primary keys of database related objects and instead passing a unique string?
LostInTangent

Mar 05, 2009 at 5:21 PM quote reply

I would go with the unique string approach. Since part of the whole objective is to provide more meaningful URLs to end users, integer/guid identifiers don't really provide them any value. That doesn't mean that you won't still need to do something along the lines of "Products/1" in situations were that makes sense. You might have resources that don't legitimately have a unique value other than an ID. For SEO purposes having a descriptive value in the URL certainly helps as well. "Products/Cups" is capable of being spidered as a resource on "cups" whereas "Products/45" isn't. Will that make a huge difference? Maybe not, but every little bit helps

There is no need to get religious on either approach, it all just comes down to which approach serves the needs of your application the best. Since routing is so extensible, you should have fun building the sitemap you want. There is soooo much more to it then what I showed in this demo since this episode was meant only to show how routing and webforms can work together. General purpose routing has plenty of awesome little features.

I doubt there will be a 10-4 episode on ASP.NET Routing specifically since it isn't a feature in .NET Framework 4.0, but I could throw together some ad-hoc screencasts and plop them on my blog (http://www.lostintangent.com) or C9.

Keep these great questions coming guys, I seriously love the 10-4 community
stevo_ Human after all

Mar 08, 2009 at 8:55 AM quote reply

3:05am to 8:41am

thats fast
LostInTangent

Jul 07, 2009 at 11:16 AM quote reply

Great to hear!
Arjang Arjang

Feb 17, 2010 at 7:10 PM quote reply

Is there a source file included with demo?

I have been trying to run this and keep getting file not found error I am using VS2010 Beta 2

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.