ASP.NET Routing or URL Rewriting?

I'm currently using URL Rewriting, but I recently stumbled upon this link on Rerouting, and it looks like it's quite simple yet powerful, and easier to implement than URL Rewriting, a "downside" probably is that configurations are not sitting on a web.config file but rather on the code itself, but I was wondering about the differences, and advantages of using one over the other.

Having read some resources about routing, I can see the differences, and now I reformulate my question:

Is it worth it to move from URL Rewriting to Routing? Are there any IIS-specific configurations that should be made? Is it recommended to use it on a ASP.NET WebForms Application, or is it oriented to other kind of projects?

Answers


IMO URL Rewriting has been a workaround in many cases. Rerouting is one of the concepts that supersede URL Rewriting in that cases. In Short: If Rerouting works in your case, you should use it.


Need Your Help

What does '#type' mean in Haskell Foreign Function Interface?

c haskell types ffi preprocessor-directive

I have found this piece of code in the Haskell sendfile package:

About UNIX Resources Network

Original, collect and organize Developers related documents, information and materials, contains jQuery, Html, CSS, MySQL, .NET, ASP.NET, SQL, objective-c, iPhone, Ruby on Rails, C, SQL Server, Ruby, Arrays, Regex, ASP.NET MVC, WPF, XML, Ajax, DataBase, and so on.