Why MVC is better than ASP.NET?
- ASP.net is the old standard for web forms.
- I know ASP.net mvc is a newer framework.
- ASP.net MVC was created in 2007 or 2008.
- The model-view-controller pattern tries to separate data, logic and the presentation of both to the user. That's one of the basic things they teach you in computer science.
- When you separate these layers, you can change the view based on the user's input without altering the presentation.
- AKA, changing buttons and menu options on a user's screen without losing the data they've put in because that is saved somewhere other than the life cycle workflow ASP.net uses.
- MVC lets you execute part of the code on the client, lessening demand on the server. And, sometimes, increasing response time as a result of the local processing.
- I had not heard that it increased performance.
- It can, but doesn't always. But MVC always has easier integration with JavaScript frameworks. And MVC is the standard of the stateless web, since it is IT agnostic.
- What is IT agnostic?
- It does not care what device it is being viewed on or browser being used.
- What other advantages does MVC have?
- MVC lets you create nested views.
- I think JavaScript or even CSS pretty much renders that moot.
- MVC provides greater control over all rendered HTML.
- Why else would someone consider MVC better? Sharepoint in ASP.net is considered an excellent resource because its developers are hardly better than code monkeys, pointing and clicking options on lifecycles and templates.
- MVC lets you separate the data processing from the interface. If you need to change the screens the user sees, you don't have to rewrite the data handling, too.
- That's a significant improvement.
- And if you don't have to rewrite the whole thing, you don't have to retest the whole thing.
Comments
Post a Comment