>>>In this case A does not seem
>>
>>Looks like you were cut off in mid-flow :-}
>
>it was a fragment of something I started to write and then rewrote. It was scrolled off screen when I hit post.
>
>I had to rush off and didn't do my usual double check. So... ooops.
>
>>This is about the only time that ViewModelA and ViewModelB need to interact and, AFAICS, this is the only other communication they need so I'll leave as is for now. But, thinking about it, it would be a fairly trivial step to combine both VMs under a 'master' VM - the XAML guys would only need to know how to bind to both bits......
>
>Your solution sounds fine to me too.
>
>I see you've decided to go ahead with Prism.
>
>Hopefully your having fun with it. <g>
>
>I hooked Prism up to AvalonDock last weekend and created a basic framework/interface for my modules. MEF auto discovers the modules and they incorporate themselves into the menus and toolbars of the framework. So far it's been surprisingly easy to code and I like what I'm getting out of it.

I started using Unity with Prism. When MEF came along I tried comparing it to Unity. In the end, although MEF looked cleaner and simpler, I couldn't work up enough enthusiasm to switch. (I also seem to recall there were a couple of features in Unitty that were useful but not implemented in MEF).

Hadn't looked at AvalonDock before. Just from skimming the codeplex site it looks as if it mimics, to a certain extent, the VS IDE ?