Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I spent the last 4 weeks reading the available material on MVC and doing the various videos and tutorials. Today I started working on an actual application (with a client awaiting to see results some time soon). I agree with the previous answers (an awful lot to learn, many many new concepts, little in lieu of 3rd party components). Still I am glad I have spent the time learning mvc. - You have to overcome your fear of row html/css/jscript which are hidden with webforms. It takes time to get used to the html tags. Once you do you will find out about the possibilities available. You will unlikely miss tags. - If you have no experience using unit tests, then I think that mvc provides for a great introduction into the possibilities that come with unit testing. - OO is much more present and "obvious" within mvc.<br> - Separation of concerns is possible and natural. You will not miss mixing gui and business logic in an aspx.cs file.<br> - No more page_load (and the n different stages). If you never quite liked asp.net's databinding, you will love mvc. I am happy not to have to do it ever again!</p> <p>Cons: - It is slow. At the beginning it is very slow. Things that take little time in webforms, can take a lot of time with mvc.<br> - Not having pages any longer is also a massive change. But once you "internalize" this (time...), you will not miss the pages. - An O/R Mappers is also needed. One more thing to learn. - There is a lot to learn and get used to, should you be interested in getting the most out of the framework. MVC is only half-mvc without unit testing. Unit testing without a mocking framework is not really possible, so you must learn that too. By the time you think you are half-way through with unit testing, you see the need to automate parts of your work, nant must be learned as well. It is just endless.... But again, once you start using these technologies you will wonder how you ever managed without.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload