What are the good points of using View Engine Aspx instead of Razor?

Question

What are the good points of using View Engine Aspx instead of Razor?

Navigation

#1 by (4 votes)

4

When I search on ASP.Net MVC , I always find all examples of views with Razor (I do not remember exactly if I saw any in aspx) and in the past I remember that I could select this View Engine when creating a new one web application (I can not remember the version of Visual Studio).

Then came the doubts:

What causes someone to use this View Engine with ASP.Net MVC ?

Is it possible to have an advantage? What?

In Microsoft's future plans, does Aspx have its place?

c# asp.net-mvc razor webforms

asked by anonymous 05.03.2015 / 18:03

1 answer

Querying the status of PayPal transactions by URL How to solve the conflict between AngularJS and Django?

score 4 · Accepted Answer

What causes someone to use this View Engine with ASP.Net MVC?

Basically, the legacy. Imagine that you want to port a large Web Forms (ASPX) system to MVC. Saving the visual layer of major changes also saves programmers from having to redo the screens.

Is it possible to have an advantage? Which?

Yes. On performance issues, Engine Web Forms is faster . In addition, Razor does not support the Visual Studio Design Editor (some companies still use this editor to make pages), which lacks the ability to program (at least initially) HTML.

In Microsoft's future plans, does Aspx have its place?

Possibly only as a legacy. It is very costly for Microsoft to keep the Visual Studio Design editor, so the idea is that this part is pragmatically discontinued.