ASP.NET Web Forms

583 WordsFeb 24, 20182 Pages
At this time there are a good deal of ASP.NET web forms coders out there who admit that they simply don’t have an understanding of ASP.NET MVC. In a lot of ways, I can associate with them. The expressive fraction that talks about ASP.NET MVC speak about it with such fervour that they make it appear like you’d have to be a idiot not to change over. In reality, the selection isn’t nearly as straight forward. ASP.NET web forms aren’t going anywhere. These methods have their right place in a web developer’s toolbox and it’s crucial to discover their strengths and flaws. In general, the ASP.NET MVC framework has a tendency to give up ease-of-use (e.g. viewstate, validation, etc.) in order to supply developers stronger control over the reins. This can be a terrific thing, but only if you take advantage of it. If not it can just as easily be a issue. With all of this, I have developed a swift metric to establish if ASP.NET MVC is right for you. The way I see it, there are three primary purposes a developer should select the ASP.NET MVC framework over ASP.NET web forms. If none of these factors are compelling to you, then you need to stick with ASP.NET web forms: To Increase Control and Extensibility As indicated out in the commentary, ASP.NET MVC supplies you much more control and extensibility options than ASP.NET web forms. You get entire control over the page request lifecycle and the ability to replace out several key items of the framework (e.g. view engine, routing,

More about ASP.NET Web Forms

Open Document