From the docs, "Razor Pages can make coding page-focused scenarios easier and more productive than using controllers and views." If your ASP.NET MVC app makes heavy use of views, you may want to consider migrating from actions and views to Razor Pages.
Razor has no ties to ASP.NET MVC because Razor is a general-purpose templating engine. You can use it anywhere to generate output like HTML. It's just that ASP.NET MVC has implemented a view engine that allows us to use Razor inside of an MVC application to produce HTML.
A Razor Page is very similar toASP.NET MVC's view component. It has basically same syntax and functionality as MVC. The key difference between Razor pages and MVC is that the model and controller code is also included within the Razor Page itself.
Razor View Engine is a markup syntax which helps us to write HTML and server-side code in web pages using C# or VB.Net. It is server-side markup language however it is not at all a programming language.
(new answer to respond to your RC2 numbers)
Thanks for the updated numbers. A few points:
debug="false"
set in web.config.How did you perform the benchmark? Was your site deployed on IIS in mode Release? Did you use the <deployment retail="true" />
section in your machine.config? Also remember that ASP.NET MVC 3 is still under heavy development so you cannot expect it to be fully optimized yet. At least wait until it hits RTM.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With