Basics of ASP.NET MVC
MVC – the Model View Controller is a framework where each component is loosely coupled with each other. MVC is not the alternate of ASP.Net web forms, but a separate framework that force to develop application in tier architecture. Whether to choose MVC framework or ASP.Net web form, it depends upon the requirement and time span. The points given below may help you to choose an appropriate technology for your requirements.
When to use ASP.NET MVC framework?
- When you want to develop SOA or 3-tier based application.
- MVC is code driven technology, when you want full control on behavior of application, this will be the better option.
- Since it is code driven, therefore it requires more time to develop and is beneficial in case of big project.When you need full control on markup language, Razor will be the most suitable and flexible.
- MVC is loosely coupled between components; therefore managing components for a project is easy. Loosely couple mechanism also gives the flexibility of parallel programming in case of large team.
- Separates Business logic, UI logic & Input logic into different components, so managing a project becomes easy. This framework also defines where to put the corresponding logic.
- Nevertheless, it keeps track of project where large number of developers are working, so that class files should be in specific unit.
- When you need more flexibility for URL rewriting which vital in SEO.
When to use ASP.NET Web Form?
- Tightly coupled, requires less code development. Therefore, it is beneficial in case of less time span.
- Advantages for small project or where it requires for Rapid Application Development (RAD).
- It is event model that preserves state over HTTP. It supports server side controllers.
- When you want benefits of server controls to avoid large amount of code lines.
- When you want to avail state management techniques.
We will discuss more about ASP.NET MVC 4 in next article.