Next week I’m coming to the UK where I’ll be spreading the MEF love at FEST 10 and in events in a few other cities. I’ll also be talking about REST and the new work we are doing in WCF to provide a better experience for building RESTful systems. In this post I share the event schedule.
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.
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!
<Goal>Post in 15 mins or less :-)</Goal>
This question which recently popped on our forums is one of the common questions we hear from customers. In this particular case, wcoenen (the person in the forums) had recently used information that he wanted to pull from configuration and pipe to a part.
About a month ago I posted some ideas around MEF and Prism together. As part of the post, I presented 2 high-level scenarios for MEF/Prism integration (and there are likely more)
Use Prism with MEF as an add-on for extensibility. That is make modules extensible through MEF.
In our last post we saw how using metadata in MEF allows us to provide additional self-describing information about exports. This has a range of uses including providing hints on how the export should be handled (such as UI location) as well as allowing us to filter out creating exports that we don’t need or which are not relevant to the current application context.
In Part I of the series we built the basics of our dashboard end ended with our app displaying a single widget. In this post we’ll show two widgets, sensing a pattern here? 🙂 We will show two, but we’ll put them in different places on our dashboard.
Note: This only applies to using MEF Preview 8 on Silverlight, it does not apply to MEF in Silverlight 4
Yes I know we never did a Preview 8 post but……
We found a bug in PartInitializer (thanks to Kathleen Dollard for finding it!)
In my last post I illustrated some of the basics of MEF through a Hello MEF dashboard app that I used in my PDC talk. In this series of posts, we’ll build that application from scratch and then go even further than we did in that talk.
At PDC we announced that MEF has is now part of Silverlight 4.
This may sound like alien speak :-), so I’ll break it down for you. It means building maintainable/pluggable RIA apps just got a whole lot easier.
What is MEF?