Tell me that difference between ASP.NET MVC and ASP.NET

Question

1.00/5 (1 vote)

See more:

Why do we use asp.net MVC instead of asp.net application. For my opinion, i was very easy to work with asp.net web Application instead of MVC.

What I have tried:

For all the code what i have tried in MVC is lightly tough for me. please tell me that the difference for both. It may leads me to undertand about MVC.

Posted 28-Nov-18 0:57am

Karthick Rajendran

Updated 28-Nov-18 2:20am

Add a Solution

Comments

F-ES Sitecore 28-Nov-18 7:16am

As suggested, there are thousands of articles comparing the pros and cons of both. If you want to find them you should get your terminology correct though, you mean webforms when you say asp.net so google for things like "asp.net mvc vs webforms" and "mvc webforms pros and cons"

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Accepted Answer · 2018-11-28T01:06:00

Solution 1

There are many articles about these subjects that you can find and read for yourself to understand what MVC adds to the basic ASP.NET structure.

Posted 28-Nov-18 1:06am

Richard MacCutchan

MadMyche · Accepted Answer · 2018-11-28T02:21:00

What you use is completely up to you.

You just need to realize that if you use an older technology there is less innovation going on with it and if less people are using it then there are less people that can help you out.
My last employer is still actively developing Classic ASP sites along with MVC versions 3 & 5. While they host all of these internally; any of these sites can go to just about any of the commercial hosting platforms supporting Windows.

ASP.NET Web-Forms require an MS stack to run on. It is based on making HTTP and the web as event-driven and having state on a stateless platform. While it was great in concept and could have been the wave of the future; the internet evolved in a way that didn't require state and events were driven in a way that did not require what MS offered.

MVC is a design principal with a firm Separation of Concerns. It is language and platform agnostic; which is huge as a project written for one platform can be ported to another without needing proprietary controls figured out.

MS decided to jump on the this along with joining the open-source community, so that developers would have options to work with. They have created a new track that doesn't require an all MS infrastructure and can have universal deployment.

Yes, there are pros and cons to both. If you want those you can read through this article which is still relevant today: CodeProject: WebForms vs. MVC[^]