MVC...why

technodrone — Wed, 06 Feb 2008 22:27:16 GMT

During the summer of 2007 my supervisor asked us to start using MVC to "so that our applications would be easier to test". I researched the topic briefly but all the examples I saw just described how to put code in the code behind page and have seperate classes for data access and business logic. We were already doing that so we didn't take action. We were at a loss as to why MVC would be of any use. 6 months later the fog starts to clear. We learned the hard way that mixing business logic at calls to a variety of other classes put together according to each programmer's style stinks. It is becoming a monster to maintain and impossible to test. Ok I get the why but after a couple of days study I still don't have a clear picture of the best approach to take.

MVC with Visual Studio 2005 fumbling for answers.

MVC...why