Did anyone ever switch a UI from something to something else?
Jun 14, 2010
When reading about MVC, MVP, MVVM,... there are mostly two big reasons for using them:
Funny thing is: Most companies I was working in projects of, didn't know how to unit test. Telling them, that it's easy to unit test an MV based app didn't even result in a strange look. Well.. except for those companies in which I heard variations of the following: "Unit. Testing. Yeah yeah,... aha... right. Great thing... However, we don't do that."
Second point: Portability. Did ANYONE of you EVER have to switch an applications UI from let's say winform to wpf? Or from wpf to ASP.NET? Or from Silverlight to Console... ?
The thing is, looking at the Patterns in Action sample, I noticed that there is one HELL of an effort to get a list of customers displayed on screen which could (...) be reduced to a couple of lines when abandoning the MV patterns. If properly written, it wouldn't be *that* complicated to port the result... at least there wouldn't be such an overhead as with MV. And nobody can tell me that there is no such overhead... or even that there isn't anything of it except for the Presentation Layer to be ported.
I would love to see some real world examples of companies who successfully worked with any MV pattern, used their advantages and really had less effort than if they used a more classical approach.
Aside from that, I love your sample and the implementation of the patterns, since they are a great compilation of invaluable knowledge. Thanks guys!!
P.S.: When is 4.0 to be released?