URL rewriting with UrlRewriter.Net, ASP.NET MVC Routing or what do you recommend?

I am just wondering if you are creating a new ASP.NET web form application in ASP.NET 3.5, which would you recommend for rewriting a URL? UrlRewriter.NET or ASP.NET MVC Routing. I used UrlRewriter.NET before and was very pleased with this.

Anyone opinions?

+3
source share
5 answers

Routing is far superior to IMHO. Instead of pretending (to rewrite URLs to keep SEO types happy), you do this (by making real URLs to keep SEO types happy). Another huge advantage is that routing is reversible - you can easily get the URL from the parameters, which is very convenient.


No, they do very different things. Rewriting URLs accepts the incoming URL and rewrites it before submitting an ASP.NET (or IIS) processing request. URL routing takes the URL in ASP.NET and displays the handler using the parameters found in the URL. Url itself never changes.

+2
source

UrlRewriter.NET - -, . ASP.NET MVC MVC.

+2
+1

Asp.Net MVC webform? , , , , , ?

Asp.Net MVC - WebForms, . , , , , , .

+1

Web forms ASP.NET 4.0 (I believe it was introduced in version 3.5 SP1) has built-in routing. It has an advantage over rewriting the modules that it is built in natively within ASP.NET, and therefore does not require the hacks to work correctly.

Thus, you should not look for MVC just because of routing.

0
source

Source: https://habr.com/ru/post/1715630/


All Articles