MEF & Silverlight 4 Beta - Part 4, Recomposition

Play MEF & Silverlight 4 Beta - Part 4, Recomposition

The Discussion

  • User profile image

    Very powerful

  • User profile image

    Where is part 5?

    Shouldn't this be already an inherent design attribute of the Silverlight platform? ...The intrinsic ability to handle bulky application parts with heuristic algorithms to prioritise which parts get loaded first?

    I must say this all seems very frustrating... to sit and waste so much time learning these "brilliant" ideas, designed to mitigate Silverlight flaws.

  • User profile image



    Part 5 is here - it's hyperlinked from the text above as well so not sure whether you're having some problem with that link or not?


    There are capabilities within Silverlight today to download XAPs dynamically and to also package up sets of functionality into related ZIP files to avoid downloading them more than once across common uses in multiple apps.


    So, it is possible to build a partitioned and extensible app with Silverlight today if you need this kind of functionality but MEF is coming along and trying to offer a pre-built, flexible, extensible, supported Microsoft framework for doing that kind of thing so you don't have to burn time/money on it.


    It's also not just a Silverlight thing - it'll be part of .NET Framework 4 for the desktop/server as well.


    For me, that's not mitigation of a flaw in either Silverlight 3 or .NET Framework 3.5 Sp1. It's a welcome addition to both platforms that takes away a bunch of "plumbing" code that a lot of application builders don't want to write so, personally, I welcome it along with other Silverlight 4 additions that broaden out the platform.





  • User profile image
    Thundar Viking

    A very good video and good basic example on adding typecatalogs and the automatic discovery by MEF of classes implementing requested interfaces through export-import functionality of MEF. The video explains how to apply [Import(AllowRecomposition=true)]

    or [ImportMany(AllowRecomposition=true)] - the AllowRecomposition setting of an import to specify that an import might change during execution time and making it possible to satisfy an import at a later stage when the program is running.


    I followed along the video in Visual Studio ("coding along") and everything in this video worked great on my setup also. Another pedagogical masterpiece of Mike Taulty explaining the wonders of MEF.


    -= The somewhat civilized barbarian =-  

Add Your 2 Cents