WebForms X MVC? Why MVC? Give me reasons to migrate my web apps to it please. Pros x Cons! Thanks!

Discussion in 'ASP .Net' started by Paulo, Dec 2, 2008.

  1. Paulo

    Paulo Guest

     
    Paulo, Dec 2, 2008
    #1
    1. Advertisements

  2. The main push for MVC is it forces separation of concerns. If you already
    properly tier you apps and treat ASPX as a UI only, you probably will see
    little benefit from MVC. But that would also make you one of a small
    percentage of devs who properly separate out concerns.

    --
    Gregory A. Beamer
    MVP: MCP: +I, SE, SD, DBA

    Blog:
    http://feeds.feedburner.com/GregoryBeamer

    ********************************************
    | Think Outside the Box! |
    ********************************************
    "Paulo" <> wrote in message
    news:...
    >
    >
     
    Gregory A. Beamer, Dec 2, 2008
    #2
    1. Advertisements

  3. Paulo

    bruce barker Guest

    Re: WebForms X MVC? Why MVC? Give me reasons to migrate my web appsto it please. Pros x Cons! Thanks!

    MVC is a advanced pattern. It separates the UI from the business logic.
    If you do not use or study design patterns then its proably not for you.

    For those that use design patterns and have used the MVC pattern in the
    past (its fairly old pattern), it nice that MS is supplying a tested
    framework.

    Reasons to use it:

    1) want logic separation.
    2) use Test First Design (the MVC framework is designed for this)
    3) want to use lots of javascript and ajax
    4) want a REST interface to your site
    5) want a simpler page life cycle
    6) have a separate designer team that edits the pages

    Reasons not to use it.

    1) unfamiliar with design patterns - may be to big to bite off
    2) want to use the visual studio designer for the site
    3) unfamiliar with native html form / server processing
    4) like the webforms event model
    5) don't want to worry about state management.

    -- bruce (sqlwork.com)
     
    bruce barker, Dec 3, 2008
    #3
  4. Good question. I haven't used it yet, and I read a lot of posts by users
    having a lot of difficulty with it. Most people will say its a much cleaner,
    object - oriented way to separate the Model, View and Presentation in an
    application, and they'd be right. But if you're happy with ASP.NET as is
    (and I am) then it may not be necessary to go through the learning curve and
    inevitable pain of mastering it.
    Peter
    "Paulo" <> wrote in message
    news:...
    >
    >
     
    Peter Bromberg [C# MVP], Dec 4, 2008
    #4
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Kumar Vijay Mishra

    PSL pros and cons

    Kumar Vijay Mishra, Sep 29, 2004, in forum: VHDL
    Replies:
    2
    Views:
    2,964
    vhdlcohen
    Oct 2, 2004
  2. Benny
    Replies:
    1
    Views:
    582
    Paul Wistrand
    Mar 1, 2004
  3. Jeffrey Todd

    Reasons To Migrate to 2.0

    Jeffrey Todd, Jun 3, 2005, in forum: ASP .Net
    Replies:
    6
    Views:
    698
    Jeffrey Todd
    Jun 4, 2005
  4. Lucas Tam
    Replies:
    3
    Views:
    2,254
    Reza Alirezaei
    Aug 9, 2005
  5. J.S.
    Replies:
    10
    Views:
    6,539
    shawpnendu
    May 20, 2009
  6. John Benson
    Replies:
    4
    Views:
    560
    Cameron Laird
    Nov 20, 2003
  7. Mr. SweatyFinger
    Replies:
    2
    Views:
    2,842
    Smokey Grindel
    Dec 2, 2006
  8. Gerald Bauer
    Replies:
    0
    Views:
    349
    Gerald Bauer
    Jul 15, 2008
Loading...