What's your choice for your next ASP.NET project: Web Forms or MVC? [closed]

Answer 1

MVC. We're going to redo an application that is SEO intensive and MVC seams to fit right in out of the box. Plus I want to hang out with the cool kids on the playground.

Answer 2

Is MVC the "flavor of the day", or does it have staying power?

I have worked with MVC, and have a vast amount of webform experience. I often wonder about the staying power of MVC.

You should consider this when choosing one or the other. What do you want to support for the entire product lifespan?

Answer 3

it really depends on the project, since i havent build anything with MVC and if the project has a short time delivery, i will probably find some hinders in MVC that could make me not to deliver the project in Time.

Answer 4

I would choose MVC since designers and developers can work in parallel on the same project. Designers can work on the view part (JavaScript, CSS, HTML) while backend developers can work on the controller code.

Answer 5

I would like to be doing ASP.Net MVC, even though I'm still very new to MVC. But it's not to be in the foreseeable future.

Answer 6

MVC FTW!, Reasons?

• Total Control over my HTML
• No Web Forms magic
• No complex page life-cycles
• Closer to the metal
• It is the natural thing to use with HTTP