Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
if you like to make a comparison between both Asp.net technologies ,it's up to you .
1- Separte Views ( UI ) - Controllers (Bussiness logic) Models (data storge)
2- Mantaince - unit test
3- menimum code writen
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
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
Hope this helps.
If you are looking to develop something fast regardless of code quality, web forms is your choice. But if you want to develop something based on international standards and third party libraries with a clean and easy to understand code, MVC is your best choice. Moreover, ASP.NET Web forms uses the control state property which adds a huge chunck of code in the view ths affecting web site loading time unlike MVC based on javascript and jQuery.
MVC provides the ability to separte the View (i.e. the UI) from the bussiness logic. That way the bussiness logic can be independently unit tested. The View also becomes very thin (i.e. with minimum code) which is good because it is hard to unit test the View.
MVC minimize your code as comapred to it's compartive techique3 tier
MVC is based upon Seperation of Concerns Principal where the architecture force us to think in terms of business logic and underlying datastore seperately. One thing which is very important is that MVC is not a new concept it has been there for years, so what prompts Microsoft to adopt this concept should be enough reason for the .net developers to follow the suite
some advantages for MVC over Webform for example there is no view state , you can use more than form ,highly integrated with Microsoft EF
MVC is the real way of web lifecycle. Web forms is a whole library that enables web development to look like a windows project. But MVC works in pipeline logic. If you develop a MVC project you can see the progress clearly (server side and client side). There are some data transfer between server and client and that is all.
Also in MVC you have the all control of generated html, so it is faster and efficient.
The main advantages of ASP.net MVC are: Enables the full control over the rendered HTML. Provides clean separation of concerns(SoC). Enables Test Driven Development (TDD)
i Think the biggest advantage is Software enginnering Principle
Separation of concerns (SoC) and Test Driven Development (TDD) With MVC, you can more easily create tests for the web side of things
one of the biggest advantage is seperation of concern i.e. the seperation of logic from the view using controller to map the views to the data (model). this maes readabilty easier and also future modification of the code. unlike code behind approach all the logic liew in the controller and all the data calls in model while the view is strictly the template that uses the model data to show mwaningful information on screen.
