An outlet for my obsession with technology
A somewhat less biases comparison of MVP and MVC
What is it called?
First off; what are we calling “Classic ASP.NET Development using Webforms and the MVP Pattern” today? I’d like to suggest we stick with a discussion of the patterns and the surrounding technology.
Component based development using the MVP pattern…or MVP for short 
and
Non-Component based development using the MVC pattern…or MVC for short
And I am aware that there are companies working on MVC components/html helpers…so what else are we going to call it? Then again you might be write…what % of “Webforms” developers are using the MVP pattern? 5%?…hmmm…anyway I am sticking with MVC and MVP until I read something better on stackoverflow.com
Don’t be such an ass
Here is the document that I presented to a client when they asked for…well a comparison of “Classic ASP.NET Development using Webforms” and “MVC”
Introduction
In the .NET world the MVC pattern is relatively new but it has been the staple development architecture for Java and Ruby for over a decade. Most of the current the debate between what technology is “better” is argued from a developer’s point of view. While the technical underpinnings of a technology can often translate to the projects success; I feel that both WebForms and MVC are mature enough that most projects will do fine with either.
ASP.NET WebForms
Through the abstraction of HTML, CSS, and JavaScript; ASP.NET WebForms attempts to recreate the experience of developing a desktop application. The entire HTTP protocol is successfully abstracted away and developers are present with a faux statefulness that mimics desktop applications. Development teams are able to use a WYSIWIG style of development.
ASP.NET MVC
Out of the box ASP.NET MVC forces developers to understand HTML, CSS, and JavaScript. There is little to no abstraction which can be a double edged sword. On one hand your development team has access to the raw power of the markup & languages that make up the web. On the other; if your development team is not experienced with HTML, CSS, and JavaScript there might be a learning curve.
Decision Matrix
|
Number
|
Topic
|
ASP WebForms
|
ASP.NET MVC
|
|
1
|
Size, Extensibility, Maintainability
|
Your project is small and your team is not experienced with MVC
|
Your project is large (experience with MVC not required)
|
|
2
|
3rd Party Components
|
Your project requires many specific 3rd party vendor components
|
Your project is not bound to 3rd party vendor components (The UI can still be very rich)
|
|
3
|
Open Source
|
Your project team is not comfortable with open-source libraries
|
Your project team is comfortable with open-source libraries (especially jQuery)
|
|
4
|
Extensibility, Maintainability
|
Your customers requirements will not change during development
|
Your customers requirements may change during development
|
|
5
|
Extensibility, Maintainability
|
Your project will never be "extended" or have a feature "added"
|
Your project maybe be "extended" or have features "added"
|
|
6
|
Testability
|
Unit testing is not required for this project
|
Unit testing is required for this project
|
|
7
|
Extensibility, Maintainability
|
|
Your project is limited in maintenance hours
|
|
8
|
Compliance
|
There is little to no concern with regard to HTML compliance
|
HTML markup compliance (compliance, screen readers, etc)
|
Notes
- The convention built into the MVC framework helps enforce a separation of concerns design pattern what helps developers built applications that are inherently more extensible and maintainable.
- If your project/company has an existing large investment in 3rd party components you should consider sticking with whatever framework the components are developed for (Webforms or MVC)
- component suites are available for both frameworks but many developers have found that jQuery, and to a less extent other open source frameworks, is a better solution for building rich UI
- The convention built into the MVC framework helps enforce a separation of concerns design pattern what helps developers built applications that are inherently loosely coupled.
- See note #4
- ….
- ….
- ….
No related posts.
| Print article | This entry was posted by Eric Polerecky on May 20, 2009 at 4:40 pm, and is filed under ASP.NET, WebForms, mvc. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
ASP.NET MVC Spark Support
about 6 months ago - No comments
ASP.NET MVC 2 supports Spark! What? hear me out. The release of ASP.NET MVC 2 includes an amazing hidden gem. You see the “Add View/Controller” dialog now takes into account a T4 directive “output extension”. Getting started with Custom CodeTemplates To get started with Custom CodeTemplates check out this excellent article by K. Scott Allen
Spark View Engine 1.1
about 6 months ago - No comments
ASP.NET MVC 2 was RTM’ed today and with the help of Jay Harris – @jayharris we upgraded our rather large codebase to not only ASP.NET MVC 2 RTM but also a new drop of the Spark View Engine built against the RTM. Since the release of Spark View Engine 1.1 RC a few weeks ago
Spark Binaries For ASP.NET MVC RC2
about 7 months ago - 4 comments
THIS IS NOT AN OFFICAL RELEASE…YET I spent the evening updating the spark source to support ASP.NET MVC RC/RC2. Well, actually I simply applied the changes that were posted to either the mailing list or codeplex. All the tests pass: Download it here: Binaries: Spark-1.0.1.0-release.zip Source: Spark-1.0.1.0-source.zip This post, hopefully, won’t be up long. No
ASP.NET MVC2 To Provide Real Spark Support
about 7 months ago - 2 comments
Ok, that might be going a little too far but it sounds like the barrier I wrote about a few weeks ago might be going away. Earlier this evening Phil Haack posted this tweet: Excited to hear this I asked a leading implementation question about honoring the output extension directive in T4 templates. Us old-timer
SOA+MVC
about 7 months ago - No comments
Disclaimer: This post is my personal reflection of a current situation. It’s not intended for any other use. Don’t use this information in anyway. Background The previous enterprise-grade SOA architected systems I’ve worked on, last decade, were Classic ASP, Java or Webforms. These systems had their presentation layer wired directly into the services. The largest,
ASP.NET MVC: Not That Open Source
about 8 months ago - 2 comments
ASP.NET MVC has one small hook into Visual Studio, the ability to right click and add views and controllers. This feature is small, hell since I’ve been using spark I almost forgot about it, that is until I started working on a simple administration section. The application has enough entities that “Right Click –> Crud”
Validating DataAnnotations
about 9 months ago - No comments
public static IList<String> GetClassLevelErrors(object instance){ return TypeDescriptor.GetAttributes(instance).OfType<ValidationAttribute>() .Where(attribute => !attribute.IsValid(instance)) .Select(attribute => attribute.FormatErrorMessage(string.Empty)) .ToList();} [TestMethod]public void TestMethod1(){ var prop = typeof (DataAnnotationsModelBinderSpike.Models.Contact).GetProperty("First"); var attrib = prop.GetCustomAttributes(true).Cast<RequiredAttribute>().FirstOrDefault(); Assert.IsNotNull(attrib);} No related posts.
Base Controller Class and TempData
about 9 months ago - No comments
Need: To pass information to every view based on an environmental variable. The specific case I ran across this need is when you want to use the minified version of your JavaScript libraries in production and the human readable in dev/QA. Solution: Create your own base controller class. Override either onactionexecuting or onactionexecuted. Populate TempData
ASP.NET MVC Routing domain.com/*
about 1 year ago - 1 comment
Scenario; you have to pass wildcard requests to a controller for processing. Think myspace.com style vanity names. Solution: Not as nice as .htaccess but it works; and I think I’m doing it write. Step 1: Add Routes to Global.asa 1: routes.MapRoute( 2: "Default", 3: "{controller}/{action}/{id}", 4: new { controller = "Home", action = "Index", id
AutoDeploy.NET to GitHub
about 1 year ago - No comments
First; When I pushed to GitHub I decided to rename the project to AutoDeploy.NET. In the hopes of keeping my sanity and in the context of working in an organization that strictly follows a 50+ page “release management handbook” I started working on AutoDeploy.NET; a deployment automation tool. As with all my personal projects I
about 1 year ago
The phrase “your developers don’t need to know [some technology] because of [our technology]” is a prime indication of where, specifically, developers will create the most bugs and where the application won’t work as designed. My problem is not running across technology that I don’t want to know or need to know…my problem generally results from companies trying to glue shit together in ways that it shouldn’t be glued together. I never once used an asp.net form. I always choose to glue stuff together myself instead, so then if it doesn’t work, I know why
about 1 year ago
If I am following you right….then I agree!
ASP.NET taught developers they don’t need to know the basic underpinnings of the internet. How huge are your balls to be able to suggest you can write an entire abstraction layer on of http/css/html/js AND that we will do it so well that the developers will need NO convention!
The complete lack of convention in ASP.NET drives me nuts!
Crap…code red gotta go…Damn bomb threats interrupting my blogging….
about 1 year ago
Bomb threats?! WTF do you work again?
about 1 year ago
um…technically I was in a government building….