At MIX, Laurent Bugnion and I had a brainstorming chat around improving on the ViewModel locator “pattern” through the usage of a MEF generic locator that allows binding via indexer properties thus removing the need for a hard-coded locator. Tonite John Papa pinged me with a similar thought.
Several weeks ago Hamilton and I recorded several episodes with John Papa on the new Silverlight TV show on Channel 9. We did not one or two but FOUR episodes on Silverlight TV covering the basics as well as some more advanced cases like using metadata views and application partitioning. We also discussed when you should and should not use MEF.
Sunday I leave to Vegas to attend my first MIX. It’s exciting to finally attend this event that has such an air of mystique around it. I’ll be speaking on how you can use MEF in SL4 to partition your applications across many XAPs in a fairly seemless fashion. My talk is short, but it’s going to be very focused. If you’ve heard of MEF but are not sure what to do with it, or you know MEF and want to see some new ways it can help you make your Silverlight apps offer a better user experience, come to this talk.
This Thursday, I’ll be joining John Bristowe and Joey Devilla to talk about composite applications, patterns, MEF and anything else that comes up. I am flexible 🙂
This is a live webcast where questions will be taken in real time, so ask away!
In the last post we migrated over to the new DeploymentCatalog. In this post we’ll look at refactoring the code to incorporate the MVVM pattern. Code from the last post is available here
There’s a ton of content out there in the blogosphere that discuss the virtues of separated presentation patterns including MVVM.
Continuing on with the series. In part III we introduced the concept of application partitioning through the use of the PackageCatalog which ships in the Silverlight toolkit. In this post we’ll take a look at a new API known as the DeploymentCatalog which ships in the box!