PRISM

PRISM course for ITI intake 35

Transcript

1. PRISM Mohamed Massoud ITI intake 35 SD software architecture
2. Course outline  What is Prism  Benefits of using Prism  How to get Prism  How is works
3. What is PRISM  Composite application framework  Break down large applications to smaller modules  Targets is WPF ,Silverlight and windows phone  Built on some design patterns Like ???  Built on separation of concern and loose coupling
4. Benefits  Reuse when you build module you can reuse it  Cross platforms that you can reuse modules between Silverlight and WPF  Extensible  Fixable  Replace component in Run time
5. How to download and setup PRISM
6. How to build PRISM application  Shell  Regions  Module Modules will contain number of ?  Views (build by MVVM)  BootStrapper it can build by using MefBootstrapper or UnityBootStrapper
7. Prerequisites for PRISM  XAML  DataBinding  Resources  Commands  Dependency Property  Behaviors  MVVM
10. Hello World Example  Create Shell  Create BootStrapper with MefBootstrapper  Initialize shell  ConfigureAggregateCatalog  Add regions to shell  Create hello world module using MVVM and MEF and inject view to the shell region  Inject module to AggregateCatalog
11. Create Shell
12. BootStrapper
13. Module Life Time
14. Modules  Initialize Mode  Dependes on Modules  PartCreationPolicy
15. Regions  There is built in regions like content and items regions  We can create our custom region  To do that I have to derive from RegionAdapterBase<T>  Implement CreateRegion method  Single Active region  All Active region  Region  Implement Adpat method  Register to bootstrapper
16. Communicate Between Modules  Loosely coupled events. A module can broadcast that a certain event has occurred. Other modules can subscribe to those events so they will be notified when the event occurs. Loosely coupled events are a lightweight manner of setting up communication between two modules; therefore, they are easily implemented. However, a design that relies too heavily on events can become hard to maintain, especially if many events have to be orchestrated together to fulfill a single task. In that case, it might be better to consider a shared service.  Shared services. A shared service is a class that can be accessed through a common interface. Typically, shared services are found in a shared assembly and provide system-wide services, such as authentication, logging, or configuration.  Shared resources. If you do not want modules to directly communicate with each other, you can also have them communicate indirectly through a shared resource, such as a database or a set of web services.
17. Event Aggregator  Pubsup  Publish  Subscribe  CompositePresentationEvent <T>
18. CompositeCommand  Usually global command  Local command register to it  When invoke all child commands invoke  Supports enablement