I’ve got a good friend Scott. He works at Microsoft, he’s a technical leader, and an awesome individual. He also lives every day plagued with being a Type I diabetic. I have known Scott for years and never realized just what he and others like him go through each day as he struggles with this illness. As a matter of fact you can spend quite a bit of time with him without even having a clue of his condition as he is so good at hiding it. Scott never complains, instead he takes action whether it is promoting awareness of Diabetes or helping to raise money to find a cure.
Recently Miguel did a post that made me smile. He talked about several libraries from Microsoft which were released under an OSS license and thus incorporated into the Mono tree and ship as part of Mono 2.8. I smiled for two reasons.
Continuing the tradition of overdue posts…….It’s been over a month since i left the MEF team. Before moving on let me say that working on MEF was a fantastic experience! The team is very excited to see all the community interest and adoption we’re seeing with MEF in commercial products, internal applications, as well as OSS projects. Thank you all for your support over these past two years. So, where did I move to?
Thanks to everyone who came out to the “Way of MEF” education day in Cupertino. I had a great time and you were an awesome audience. I really appreciate all the great / in-depth questions. It showed that you really were keeping along. I also enjoyed all the different side conversations, and all the times you guys overwhelmed me at the breaks. I really do love this stuff!
On Saturday June 12th I am stoked to be coming to the SF bay area on behalf of the Bay.Net UG where I’ll be delivering a full day on MEF! We’re going to cover a world of topics as you can see from the list in this post.
You might have missed it, but a few weeks ago MEF V1 shipped in .NET 4.0 and Silverlight 4! As a team we’re really happy to have seen MEF hit the wild. We believe MEF helps you to build better applications that are easier to extend.
The information below was wrapped up in my previous post on DeploymentCatalog. As a bunch of folks have been asking questions on this, it seems worth to rip out on it’s own.
A few caveats about DeploymentCatalog.
DeploymentCatalog is a very exciting addition to the MEF box.
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.