I'm looking for an URL-rewriter to use in my web-site. Does anybody suggest the best one I should use?
+2
A:
Nothing better than Scott Guthrie's tips and tricks about Url Rewriting with ASP.NET. The article suggests some good products to use like :
- UrlRewriter.net, open-source.
- UrlRewriting.net, open-source.
- Ionic's ISAPI Rewrite, open-source, for IIS 5/6.
- Helicon Tech's ISAPI Rewrite, $99, for IIS 5/6.
Moayad Mardini
2009-09-06 11:59:29
Should also try Managed Fusion URL Rewriter and Reverse Proxy at http://urlrewriter.codeplex.com
Nick Berardi
2009-09-06 14:52:03
+2
A:
You can try the route engine available in .NET 3.5 SP1. It's used by ASP.NET MVC.
Check out here: Routing with ASP.NET Web Forms
The upcoming ASP.NET 4.0 will also bring some better support for routing with WebForms: ASP.NET 4.0 WebForms Routing – Part I
Developer Art
2009-09-06 11:59:39
Aggree - Since asp.net has build in routing now, you should use that. I'm using it in a .net 4.0 project, and it works beatifully. An because it's build into the framework, you don't need hacks to get postbacks to work properly.
Pete
2009-09-06 12:07:31
Routing is not a URL Rewriter. You can't normalize your domain to www. You can't map legacy urls. Routing is for new .net projects only.
Nick Berardi
2009-09-06 14:56:40
A:
If you need rewriting in IIS, I use Helicon ISAPI ReWrite 3, works really well, cheap license.
Andrew Bullock
2009-09-06 12:00:35
+1
A:
Since you did not ask specifically for a module written in managed code nor did you constraint IIS to a specific version, I going to recommend Microsoft's own URL Rewrite Module, a module implemented in native code specific for IIS 7.0
Alfred Myers
2009-09-06 12:08:03
A:
I used Helicon too and was satisfied. AFAIR they have a free version that may be sufficient for your needs.
Benny Halperin
2009-09-06 12:38:06
+1
A:
I am really a bit shocked to see people recommending using some 3rd party tool for this, or even buying one!
It's pretty trivial to implement yourself; just make sure IIS maps wild-card requests to ASP.NET, then implement 'BeginRequest' in the global.asax; check for the style of url that's coming in, and then create the 'real' url and use that! Easy, and shouldn't take more than 20 mins to get a simple sample working. Then you can just adjust as needed ...
Noon Silk
2009-09-06 12:49:40
+1
A:
It seems that:
Managed Fusion URL Rewriter Seems to be the most updated tool because it says: Full .NET 2.0, 3.0, and 3.5 support. Full support for IIS 6.0 and IIS 7.0 (including integrated pipelines). Many other tools do not play nice with iis7 and do not allow integrated pipelines. http://www.managedfusion.com/products/url-rewriter/
Scott Guthrie's article, was great when it was written. However it's highly outdated today and I would no longer recommend the tools he suggests.
aron
2009-10-14 15:40:36