Beautiful URL:s with ASP.NET (we're not there yet)

Some time ago I wrote about how to do URL rewrite with ASP.NET (and about the problems that are involved). Many developers has tried to tackle the problem and I will not go to ddep into the technical stuff this time. I will how ever save a few new links I found on the subject.

First an article that isn't related to ASP.NET but shows how well-designed urls should look like.

Then an link to an Wiki completely dedicated to well designed urls, where you can read "ASP.NET - Well Designed Urls Wiki".

My conclusion is that it's probably smartest to wait until IIS 7 is released. Unfortunatly it doen't seems like we will get this web server for Windows 2003. We will probably have to wait for the new Longhorn server.

IIS 7.0 will have much better support for URL-rewrite as you can read on Scott Guthrie's blog:

Several people have asked why the built-in URL Mapper in ASP.NET 2.0 doesn't support regular expressions. There were actually a few reasons for this -- one of the big ones being that just about the time we were about to consider adding it my team started also working on IIS7. We realized that a full-featured version would want/need to take advantage of some of the new features in IIS7 as well as the support all content types (in particular -- images and directories). So we postponed making it feature rich until a future version.

I am rather happy that I havn't started to try to rewrite URLs with IIS 6 yet, especially when I read reports as "Making URL rewriting on IIS 7 work like IIS 6".

The question is if one really can wait. To have nicely formatted URLs is really tempting, especially from an SEO-perspective. But if you are going to use one of this tecniques just bear in mind that you might have to redo everything once IIS 7 is released.

If you want to have some thought from someone who has started using URL-rewrite with IIS 7 on Vista, you can read Dennis blog.

Comments

[…] Jag älskar att utveckla i C# Asp.Net och kommer definitivt forsätta att satsa på denna teknik. Men allt kan ju inte vara perfekt. Den största bristen i ramverket enligt mig är definitivt att det inte finns något inbyggt stöd för URL-omskrivning. […]
What Scott Guthrie said describes exactly the type of situation I ranted about in my post(s) "Microsoft's Obsolete Process and Release Cycle": http://www.mikeschinkel.com/blog/microsoftsobsoleteprocessandreleasecycle/"> http://www.mikeschinkel.com/blog/microsoftsobsoleteprocessandreleasecycle/ The decision by Scott and his team to postpone the feature affects all ASP.NET developers and most of the users of ASP.NET apps, and it does so for probably, what, five years? This is why open source is kicking their proverbial behind; when open-source sees a small problem that creates so many negative effects, they generally jump on it and fix it. Not so with Microsoft; they schedule it for the next major version to be released half a decade later. I tell you, this is going to be part of their downfall. Can you tell this frustrates me?!?!?
Please fill out all the fields.

*
*