>>>>I just received a "Microsoft Community Contributor Award" for 2011 in my email.
>>>>
>>>>I assume it's for the answers I give in the WPF forums over on MSDN.
>>>>
>>>>Not sure how big of a deal that is, but it sure made my day. <g>
>>>
>>>Congratulations.
>>>Are you getting to spend enough time with WPF these days?
>>>I've been shunted off to webby stuff so some Silverlight - but it's not the same....
>>>Should be back on WPF full-time within the month - but I thought that 3 months ago :-{
>>
>>Doing quite a bit, and loving it. <g>
>>
>>Started moving my libraries over to Prism and using it's MEF capabilities in January. I still have a lot of back end stuff in VFP, but the front end is all moving over to WPF.
>
>I'm afraid I'm in two minds about Prism....
>Started using it but, in a lot of design scenarios, I'm not convinced that the benefiits outweigh the extra work and planning that is involved.
>Seems to me that a project has to be BIG and involve a LOT of people before there is a clear advantage.
>But, as usual, I could be wrong :-{

Like a lot of things, I forced my self to try it because when I looked at it, it was way too confusing and I felt stupid for not understanding it. <g>

Once I did understand it, I liked a lot of what I saw.

To a degree you can pick and choose how much of prism you want to implement. I really like their implementation of commanding and event handling, so I use that everywhere. Once I wrapped my head around MEF, I found I liked the modularity it provided, so I am taking advantage of that in my base libraries. I also had a project in which I wanted to be able to use some form of add-ons, MEF does make that possible.

I don't use the IModule interface or Unity, so I can't comment on those.

The View injection and Navigation has been more of a mixed bag. I have a bit more of a love/hate relationship with that part of Prism. I am using it in certain areas, but not everywhere. I think over using it creates more problems than it solves.

Overall, my biggest complaint is that it makes it harder to discover what the code is really doing. It tends to hide which module is actually implementing the interface you are using. And, that I do few as a rather nasty problem with using MEF or prism.

Most of my projects are large enough that I tend to forget what I've done, so that's kind of like having lot's of people. <g>