which to select MVC 3 or ASP.NET C#

Question

1.00/5 (1 vote)

See more:

Hi,
I need to build a big Web application to access an Oracle Database (insert, update, select) and show a crystal report.

I have VS2010 and I would like a suggestion about which project type to use for building this web app; MVC3 or ASP.NET C#.

Thank you.

Posted 11-Feb-11 4:03am

TheCodeVB

Updated 11-Feb-11 5:29am

jim lahey

v3

Add a Solution

Comments

Manas Bhardwaj 11-Feb-11 10:55am

changed title -> witch to which ? :)

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)

TheyCallMeMrJames · Accepted Answer · 2011-02-11T04:06:00

Solution 2

If you're using MVC 3 you'll still be running on ASP.NET.

MVC is a framework that leverages ASP.NET, so you get the benefits of the established platform with (IMO) a better view engine and better separation of concerns. Auth/Auth is very easy in ASP.NET.[^], and therefore in MVC as well.

MVC 3 also provides the Razor view engine, which is slick. If you're not opposed to learning a new syntax and you're comfortable with the MVC design pattern, I would recommend MVC 3.

If you prefer event-driven programming and want "free" viewstate management, go with ASP.NET sans MVC.

For the scope of the project and the tooling available, I'd choose MVC 3.

Cheers.

Posted 11-Feb-11 4:06am

TheyCallMeMrJames

Updated 11-Feb-11 4:07am

v2

Comments

OriginalGriff 11-Feb-11 11:15am

The OP posted as an answer:
"And can I update DataBase without installing Nuget Lib. Package?
I'm getting Access Denied when try Installing PowerShell 2 needed by VS2010 to manage Package.

I'm testing with ADO.net Entity Framework."

TheyCallMeMrJames 11-Feb-11 11:53am

(thanks for the move, Griff)
No, you don't need nuget. Nuget is just a package installer. You can find the downloads separate of it. For the access denied, try running the installer with elevated privileges. Cheers.

Sergey Alexandrovich Kryukov 11-Feb-11 13:52pm

Good Answer, Mr. James, my 5; and the question is amazing in its illiteracy.
--SA

Nish Nishant · Accepted Answer · 2011-02-11T04:05:00

Solution 1

MVC 3 is still ASP.NET. So essentially your choice would be whether you use MVC 3 with ASP.NET or roll your custom ASP.NET code out. Read up on MVC 3 and see if it's the sort of thing you and your team want to move forward with.

Here's a 2 year old article that discusses the pros and cons of using ASP.NET MVC. Keep in mind that the article may be outdated now and was probably written for an older ASP.NET MVC version:

http://www.ytechie.com/2008/10/aspnet-mvc-pros-and-cons.html[^]

Posted 11-Feb-11 4:05am

Nish Nishant

Updated 11-Feb-11 4:09am

v2

Comments

OriginalGriff 11-Feb-11 11:15am

The OP posted as an answer:
"And can I update DataBase without installing Nuget Lib. Package?
I'm getting Access Denied when try Installing PowerShell 2 needed by VS2010 to manage Package.

I'm testing with ADO.net Entity Framework."

TheyCallMeMrJames 11-Feb-11 13:02pm

From the cons on that site, they don't look applicable to the above poster. New site, if they can control the IIS version in deployment they'll be fine. SEO is no longer an issue with MVC. Cheers.

Nish Nishant 11-Feb-11 13:12pm

Thanks.