ASP .NET upgrade to .NET or move to MVC [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. 开发者_如何学Python Closed 9 years ago.

I'm fairly new to the .NET ASP and MVC. My company has developed an application using ASP2. They are considering upgrades:

I'd like to know what the big advantages would be in moving to ASP .NET 4 and also would there be even greater advantages in using MVC4.

Just some background. The application is internal and will not face the outside world. It's not a big application with 3-4 users / time at the most. Most of the application is made up of screens used to edit detail records and some reporting screens.

Thanks in advance

Richard

---

ASP.NET WebForms on the .NET Framework v3.5 or higher gives you a set of new features to quickly create CRUD functionality. One example would be "dynamic data", see http://www.asp.net/dynamicdata. Also, as you might know, there is a shipload of integrated data controls like DataGrids, EditGrids and others available to use.

Generally, ASP.NET WebForms provides easy-to-use and rich out-of-the-box controls. Using those, you can quickly develop working websites without caring much about the exact HTML markup, speaking URLS (SEO) and so on. This might be totally okay for a small-scale intranet application though.

In MVC you have total control about the HTML output but in exchange you will have to build complex controls manually, including JavaScript functionality and more. MVC applications are often cleaner and easier to maintain on the long run since the framework offers a unit-testable and extensible architecture that forces a separation of concerns.

From what you said about your project, I think that you'll be fine with ASP.NET WebForms, especially since you seem to have experience in WebForms development. MVC definitely takes some time to learn.

The current version of MVC is 2 by the way. Both ASP.NET WebForms (commonly and wrongly refered to as "ASP.NET") and ASP.NET MVC are build on top of the ASP.NET Framework, whose current version is 4.0 :)

---

What reason do you have to change this application from ASP one to ASP.NET? If you think about change why does your application should be a web one at all if it is internal application, WINFORMS maybe?

MVC is a way to create applications not "better framework" that most of ppl think. Everyone talk about MVC just because it is fancy new keyword ( already not) in google and new programmers think it is something special and worth using. The one and only thing you can achieve with MVC on your Intranet site is unit-testability which probably is not even needed for your small application which basically edits and shows users same as for 99% of web applications. Noone ever gave proper why you should use MVC...

Again there is no reason to change already existing application unless you have new requirement which you cannot make in ASP whatever version you have.

---

I have been developing web apps in both WebForms and MVC3(4). In WebForms i always had problem with understanding what is going on underneath all that abstractions that Microsoft put there for us, you never had complete control in executing your code. In the other hand with MVC you really program with true nature of HTTP and not by quasi environment with state that WebForms provide. For your internal app I would suggest MVC if you want clear separation of duties and if you want to learn something new that will be useful in future. You will end up with more testable and maintainable web app, and that mean BETTER web app.