Menu
I know the difference between ASP.NET webforms and ASP.NET MVC and I've seen quite a few videos explaining that they both run on top of ASP.NET (and I've used both). However, my question is, how would one develop right on top of ASP.NET without webforms or mvc.net? Would this be the equivalent of having a project with only .ASHX files?
390
Asp.Net Web Form has built-in data controls and best for rapid development with powerful data access. Asp.Net MVC is lightweight, provide full control over markup and support many features that allow fast & agile development. Hence it is best for developing an interactive web application with the latest web standards.
Web forms are part of the ASP.NET web application and are included in the visual studio. This web form provides us the ability to develop web-based GUI applications. In ASP.NET, you can write reusable code and use it in other places without having to write the code from scratch.
Solution #1: ASP.NET Core Razor Pages.
ASP.NET 1.0 and 1.1 originally consisted of a class library and templating markup (Web Forms). This was a natural extension of ASP 3.0, where HTML and VB code were intermixed in an .ASP file.
The class library is what I would consider the "straight" ASP.NET framework. IMHO, the System.Web namespace represents the efforts to incorporate "ASP" into the .NET framework. You get the top-level objects like HttpContext object and its static properties, as well as a couple objects that do the lifting of the ASP.NET processing pipeline, IHttpModule- and IHttpHandler-derived classes.
Ostensibly, you could invent your own markup language and write an HttpModule (among other components) to render the responses. This is probably why the System.Web namespace has grown to include code for Web Services, AJAX/JSON, MVC, and in .NET 3.5SP1, ASP.NET dynamic data.
My 2 cents.
125
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
