It’s been a long time I have been working as an ASP.NET developer and I do enjoy writing web apps using web forms.
In 2008 Microsoft came up with something called as ASP.NET MVC and I was quite amazed about the fact
“Why one more ASP.NET technology required”
and many people still pondering same.
|Many people say ASP.NET MVC replaced ASP.NET Web Forms.
But that’s not true. Both have their own pros and cons
Nobody can tell or teach us what to use and when, but we can discuss about some facts which will help us to make choice between both of them. And this article contains same.
||We also try to find answers for some questions like,
- What is ASP.NET?
- What is ASP.NET Web Forms?
- What is MVC?
- What is ASP.NET MVC?
If you are advanced or experienced ASP.NET MVC developer, who already know MVC very well then this article will help you to revise your concepts.
||Microsoft initially came up with something called
Visual. With the help of technologies like Visual Basic, Visual C++ Microsoft enabled RAD (rapid application development) of Graphical User applications. Features such as Drag and Drop and intellisense made developers to focus more on the business functionality of the application rather than on UI design.
But this technologies were limited to desktops, when it comes to web the only option left with Microsoft was ASP.
When we say web technologies, we have classic ASP, php, jsp,ROR, ASP.NET Web Forms, ASP.NET MVC and many more.
Classic ASP is one of the web technology introduced by Microsoft. Biggest pain point with the classic ASP was spaghetti code and
Let assume a scenario where you have some text boxes and a button. On button click you validate the data with the server and if validation succeeds data will be stored into database and in case it fails, error message will be shown to user in the form of red colored label.
You know what’s the biggest problem with this scenario is? You have to do lots of stuffs by your own.
- First make the self-post back by setting form’s action attribute’s value to same page.
- Text box values are going to be cleared on button click, so only choice left will be retrieving values from posted data.
- In case validation fails you have to explicitly
- Set all values back to the corresponding text boxes from posted data
- Show error message.
(Using Ajax is an alternate method. Here I was trying to explain the manual work need to be done with classic ASP)
Technologies like Visual Basic are limited to standalone applications, when it comes to web, only option left with Microsoft is classic ASP.
When we talk about Web and Desktop, two things which should be considered are
- How state management works?
- How request/response works?
Web works on HTTP which is completely a stateless protocol. We will be having request and response independent of previous request and response. Unlike desktop no variable values will be preserved and no complete event driven programming model. Like desktop it will wait for user inputs but every user input and interaction act as a new request (get/post) to server.
Finally Microsoft came up with something called ASP.NET Web Forms, considering rapid application development and easy learning in priority.
ASP.NET is a Microsoft’s Web application framework built on Common language runtime for building dynamic web sites using one of the programming languages like C#, VB.NET etc.
It supports 2 models Web Forms and ASP.NET MVC.
Microsoft first brought out ASP.NET Web Forms from ASP which solved lots of problems by creating higher level abstraction over stateless web and simulated stateful model for Web developers.
In web forms concepts like self postback (post form data to same page) and ViewState (maintain control values during postbacks) are introduced. And the most interesting part is it’s not required to write even a single line of code.
With Web Forms Microsoft tried to bring the Visual Basic model into web.
Let’s talk about advantages and disadvantages of Web Forms.
- Web Forms supports Rich server controls.
- While working with pure HTML you might have noticed, Things are not always same at all place.
A UI which looks great in IE might distract in Firefox or vice versa.
- Many server controls like GridView and ListView comes up with data binding capabilities reducing lots of efforts and codes being written.
- Support for ViewState - You might have heard couple of times “HTTP is a stateless protocol”. Normally controls will not retain their values between requests. But in Web Forms statefulness is achieved by storing last known state of every control within the client page itself in the form of hidden field called ViewState.
- Event driven programming -
With the help of
Microsoft introduced event driven programming in internet world.
- Code behind
- Self postback mechanism (posting back form to the same page)
Developer will no more rely on POST, GET methods for handling user interactions with server.
For example she/he will drag control (say button) to page, just double click it to generate the code block for handling user’s click on server, write down the logic inside it. That’s it. She/he is not concerned with what happens inside.
- Rapid application development
- I don’t think any explanation is required for this. Rich server controls, Event driven model and ViewState increases the development speed by great extent, Developer will be abstracted from lots of the background complexities.
- Project Architecture
There is no fixed predefined Project Architecture for creating web applications when it comes to Web Forms. Developers have full flexibility for choosing their own architecture.
One may use basic three layered architecture dividing the system into UI, Business layer and Data access layer or a more advanced one like
Model-View-Presenter. Even one may choose only code behind and write everything there which is not at all considered as good practice.
Code behind is tightly connected to UI, ending up with some presentation logic.
- Unit Testing
In Web Forms code behind ends up with lots of event handlers, making automatic unit testing an impossible task.
Note: as per my knowledge even with the help of mock testing (using MOQ or rhinomoq) we can’t mock ‘sender’ and ‘eventargs’ in event handlers.
And when we talk about employing TDD, unit testing code behind (presentation logic) becomes very important.
ViewState becomes solution for some problems with classic ASP but it also becomes an issue. ViewState is stored in the page itself resulting increased page size so reduced performance.
Let’s talk about another example where we are supposed to build 2 UI
Now most of the code behind logic is going to be same for both screens.
- Taxable Employee screen
- Nontaxable employee screen
One solution will be, add some if conditions in code behind and create a single UI.
- This will violate
Single Responsibility principle which says there should be only one reason a software entity to be changed, because in this case employee form will be changed whenever any of the taxable/nontaxable information changes.
- Secondly it may possible that both UI
- SEO –
URL’s are pointing to fixed ASPX pages which might be decorated with some query string. They are not user friendly and affect SEO.
- Less support for parallel development - ASPX page are tightly coupled with code behind files. So it’s not possible that 2 different developers are working on one section (one on aspx and one on code behind) at same time.
ASP.NET 4.0 has come up with some good features to overcome some of the above problems
- ViewState: Provide the way to disable or control the size of the ViewState.
(But there is no compulsion or fixed rule that will say to do so.)
- URL routing: Using URL routing we can provide our own URL in lieu of the physical path of the page.
Even after the evolution of the revolutionary features of ASP.NET,
- It was still not able to solve the problems of unit testing
- I never saw any ASP.NET Web Form developer who tries to disable the ViewState.
(It’s my perspective, no hard feelings please.)
MVC is an architectural pattern which is has been around for sometimes now.
Many are using it including Java. It’s not new concept which Microsoft brought it up.
ASP.NET MVC is something we should talk about. But prior to that lets clear some terminologies including MVC.
- Patterns - In simple words Pattern is a solution to a problem in a context.
- Architectural Patterns - Architectural Pattern is something which solves our problem at sub system level or in short module level. It deals with the problem related to architecture of a project. It tells us how we can divide our systems and especially why. We make Class libraries, Components, Web services to solve the problem.
When we talk about application we will be having input logic, business logic and UI logic and MVC is an architectural pattern which let us develop an application having loosely coupling between each of these elements.
The main intention behind MVC pattern is separation of concerns. It makes presentation or UI ignorant of business and user interaction logic.
According to MVC system should be divided as M (Model), V (View) and C (Controller).
- Model is considered as smart and handles the Business rules, logic and data and will be independent of other parts of MVC (controller and View).
- Controller receives and dispatches the request in short it handles the user interaction and input logic. It knows about both Model and View.
- A view is considered as dumb and is an output representation of model data. It may be an excel sheet, a web page showing list of records or just a simple text. View knows about only Model.
What is ASP.NET MVC?
ASP.NET MVC is a Microsoft’s one more Web application framework designed with separation of concerns and testability in mind. It is built on CLR and completely based on MVC architecture and so we think in terms of controllers and Views.
ASP.NET doesn’t have support for ViewState and server controls, so we get feel of old web here.
Let’s talk about Advantages and disadvantages of ASP.NET MVC
- More learning effort - Absence of event driven programming model and ViewState makes ASP.NET MVC a very difficult framework for developers with no or little experience in web application development.
How ASP.NET MVC works
- User makes the request for some resource in server (by putting some URL in the browser).
- Request comes to controller first (routing engine is the one who is responsible for deciding which request will be handled by which controller. In this article we won’t talk in depth about this behavior).
- Controller if required talk to model for data.
- Model operates on database (or on some other data sources) and return data (in form of business objects) to controller.
- Controller chooses the appropriate view (like say Customer view which will may contain some html tables, drop downs, textboxes…).
- Controller passes the data (model data retrieved in step 4) to chosen view(in step 5), where data will be populated as per convenience.
- Controller sends back view to the user.
This was for get request, same happens for post. Only instead of putting URL in the browser user will do some action on already requested page and flow start with the controller. Actions like clicking button, changing drop down value etc.
Each can be the “best choice” for a particular solution depending on the requirements of the application and the background of the team members involved. What to choose and when has more to do with business prospective than which one is better than other.
When facing a decision to choose between ASP.NET Web Forms or ASP.NET MVC it is important to know that neither technology is meant to replace the other.
Two important factors you should consider while making the choice is
- Rapid application development -
If you want to develop anything rapidly ASP.NET Web Forms is the only chance you are having, you can’t even consider for ASP.NET MVC for RAD.
(Reasons for RAD may be anything like client is not paying too much, or application is going to be used for only one or two months and won’t require much maintenance.)
- Unit Testing - If automatic unit testing is most important factor for you MVC will be best for you.
Other than these, what you can do is, write down all your project requirement and try to compare them with Pros and Cons of both Web Forms and MVC and if possible try to ask yourself following questions and point MVC and Web Forms accordingly
- Does your team have good experience with Web Forms or Windows Forms?
Well, if yes then probably learning ASP.NET MVC is going to be a tedious task for team, because developers have been used to with ViewState and event driven programming by now and migration is going to be a difficult task.1 point to Web Forms.
- Does your team have good experience with ASP.NET MVC?
If yes ASP.NET MVC get 1 point
- Does your team have experience on ASP or non-Microsoft technologies such as android, ios, JSP, ROR, PHP?
If you have been JSP or ASP developer prior then you might be familiar with HTTP get and Post and even u might have hands on with MVC because most of them use MVC by default. It gives 1 point to ASP.NET MVC.
If Yes, MVC gets the point because you get complete control over HTML. 1 point ASP.NET MVC.
- Looking for good performance?
With no support for ViewState ASP.NET MVC provides good performance gain over traditional ASP.NET Web Forms.1 point ASP.NET MVC.
- Planning to reuse the same input logic?
If yes stick with MVC.
I think you should have equipped with enough information to make a decision what is best for your project. The complete decision depends on your team and project requirement.
Hope all of you enjoyed reading this article. Thank you for the patience.
For technical training related to various topics including ASP.NET, Design Patterns, WCF and MVC contact
SukeshMarla@Gmail.com or at
For more stuff like this click here.
Subscribe to article updates or follow at twitter @SukeshMarla
Click here for see MVC video step by step.