PRISM 4.0 TRAINING KIT Hands-On Lab Using MEF as the Dependency Injection Container汇.docx

PRISM 4.0 TRAINING KITHands-On LabUsing MEF as the Dependency Injection ContainerLab version:1.0.0 Last updated:11/19/2010ContentsOverview3Exercise 1 - Loading Modules Using MEF Catalogs4Task 1 – Creating the Application Bootstrapper4Task 2 – Loading Modules with Type Catalogs5Task 3 – Adding a Region to the Shell6Task 4 – Showing a view in the Shell7Exercise 2 - Registering views using the ViewExport Attribute9Task 1 – Creating a view inside the shell project9Task 2 – Decorating a view with the ViewExport Attribute10Exercise 3 - Using Remote Module Loading12Task 1 – Creating the new ModuleB13Task 2 – Creating a XAML ModuleCatalog and Updating BootStrapper to Remotely Load ModuleB15Exercise 4 - Monitoring Download Progress of Modules18Task 1 – Configuring a Module to be Loaded on Demand18Task 2 – Adding a Download Progress Indicator19OverviewThe Prism Library provides two options for dependency injection containers: Unity or MEF. Prism is extensible, thereby allowing other containers to be used instead with a little bit of work. Both Unity and MEF provide the same basic functionality for dependency injection, even though they work very differently. Some of the capabilities provided by both containers include the following:They both register types with the container.They both register instances with the container.They both imperatively create instances of registered types.They both inject instances of registered types into constructors.They both inject instances of registered types into properties.They both have declarative attributes for marking types and dependencies that need to be managed.They both resolve dependencies in an object graph. MEF provides several capabilities that Unity does not:It discovers assemblies in a directory.It uses XAP file download and assembly discovery.It recomposes properties and collections as new types are discovered.It automatically exports derived types.It is deployed with the .NET Framework.Task 1 – Creating the Application Bootstr