The Composite Application Guidance (Prism) for WPF is designed to help you more easily build enterprise-level Windows Presentation Foundation (WPF) client applications. This guidance will help you design and build flexible composite WPF client applications – applications that use loosely coupled, independently evolvable pieces that work together within the overall application.
Kogman Gal is a senior consultant and experience trainer at John Bryce Training, specializes in Microsoft technologies with an emphasis on the .NET development and Architecture . Has a lot of experince in Projects in the 3.5 Framework enviorment.
|
Module 1: Why Composite WPF?
- Problem background
- Hello World Composite WPF
- Aplication Quality Matrics
- Common Scenarios
- CAB, SCSF vs. Composite WPF
|
|
Module 2: Application Startup
- Bootstrapper workflow
- Bootstrapper Config
- Shell Options
- Composite Application Library Services
|
|
Module 3: Module Concept
- Designing a Modular System
- What is Module?
- Module lifecycle
- Statically vs. Dynamically Loading
- Module Loader Service
|
|
Module 4: Regions
- Region Manager
- IRegion interface
- Region Adapters
- Custom Region Adapter
- Scoped Regions
|
|
Module 5: Views
- MVC vs. MVP
- Building a View
- Composite Views
- Wiring Views Using Dependency Injection
- Views, Regions and Shell
|
|
Module 6: Commands
- Why Command?
- Delegate Command
- IActiveAware Interface
- Composite Command
- Registering and Unregistering Composite Commands
|
|
Module 6: Event Aggregator
- IEvent Aggregator
- Composite Wpf Event
- Subscribing and Unsubscribing to an Event
- Subscription Filtering
- Publishing an Event
|
|
Module 7: Container & Services
- Subscribing and Unsubscribing to Service
- Core Services
- Application-Specific Services
- Subscription Filtering
- Publishing an Event
|
|
Module 8: Tracing & Debugging
- Tracing
- Debugging
- Best Practices
|