This is a follow up from my previous post on Composite extensions for Win Forms.
Brian Noyes just posted a set of Composite Extensions for WinForms which includes a working and very simple (see below) sample.
The past few weeks, the momentum has picked up around samples using MEF. In my last post I mentioned a few. Now today two great posts. First, Brad A (my awesome boss) has gone and done a really nice MEF 101 post.
A few months ago I wrote an MSDN article on the new Composite Application Guidance (which will always be Prism to me 🙂 ) which was just published. In the article I talk about Composite Applications in WPF in general, several design patterns in play,
Blaine and my old team are at it again, and this time it’s for Silverlight. If you are building composite applications in Silverlight, they need you! Head on over and take this quick survey to help them to prioritize on where to focus for the new guidance.
A few weeks ago I had a chance to chance to chat with the gang over at Herding Code on all of the above. I was in a particularly talkative mood after coming from a full day of presenting at Tech-Ready, so I'll warn you that there might be some rambling.
Several months ago, Brian Noyes and I delivered a talk on Composite App Guidance AKA Prism at Tech-Ed USA. In the talk we discuss the essentials of Prism and do a bunch of demonstrations (well Brian did) of how to use it’s various components.
Before I go any further, we shipped! :-)
In the development of the Composite Application Guidance one area that we have labored intensely was around documentation. Documentation was so high on our priority list, that we deliberately reduced the number of bells and whistles in order to allow us to properly document what we had.
Today we received the following question / comment on our forums around our strategy for supporting multiple containers in Prism. This is something that I believe is on the minds of other folks using Prism. Below is a portion of the thread which you can access here