>>Yeah, I think the UI agnostic thing is just in terms of the VM being testable and the design guys not needing to know more about the data than a set of exposed properties and maybe a design time repository.
>>
>>I've been looking at some of the "light" frameworks as well ( MVVMLite, Caliburn Lite etc ) and also Cinch ( kind of in a niche of its own)
....
>>AAAARGH!
>
>I have a horrible feeling that if you explore all the options in enough depth you would end up realizing the shortcomings of each and decide to write your own. Better to pick one and plough on out of ignorance? (At least they all have source code available so they can be tweaked in an emergency...)
>

I am moving more and more from the idea from having the fwk doing everything developed by one vendor -
even with vfp fwks there was the need to tweak at the fwk level (but perhaps I am a compulsive tweaker...)
and with java/.net fwks spanning greater areas I see more and more benefit in the python approach to take well-defined
building blocks and glue them together. Write the necessary to glue in a different component if necessary.

my 0.02 EUR

thomas