4
When researching about ASP.Net MVC, I have always found all the examples of views with Razor (I don’t remember exactly if I saw any in aspx) and in the past I remember that it was possible to select this View Engine in the creation of a new web application (I don’t remember the version of Visual Studio).
Then came the doubts:
What makes someone use that View Engine with ASP.Net MVC?
Is it possible to have some advantage? Which?
In the future plans of Microsoft, Aspx has its place?
4
Basically, the legacy. Imagine that you want to port a large system made in Web Forms (ASPX) to MVC. Saving the visual layer of large changes also saves programmers from having to redo the screens.
IS. On performance issues, the Web Forms Engine is faster. In addition, Razor does not support the Visual Studio Design editor (some companies still use this editor to make pages), which eliminates the ability to program (at least initially) in HTML.
Possibly only as a legacy. It is very expensive for Microsoft to keep the Design editor of Visual Studio, so the idea is that this part is pragmatically discontinued.
I don’t think he’s referring to Webforms, as much as we usually associate the *.aspx extension with him. Although ASPX View Engine has the same extension of Webforms and has the same style, it is not possible to reuse a Webforms so directly.
I agree, but between making a migration to ASPX and to Razor, the move to ASPX is much less costly.
Browser other questions tagged c# asp.net-mvc webforms razor
You are not signed in. Login or sign up in order to post.
The future is to improve Razor with Tag Helpers http://www.hanselman.com/blog/ASPNET5VNextWorkInProgressExploringTagHelpers.aspx
– Maniero
@bigown, thank you so much for Link, this Tag Helper for me was the best news of the day.
– Tobias Mesquita