Architecting WPF Applications
Download as PPTX, PDF1 like2,479 views
This document discusses various architectural patterns and considerations for building WPF applications. It covers topics like inductive vs deductive UI, navigation patterns, presentation patterns like MVVM and MVP, UI composition, inter-view communication through events, dependency injection, partitioning applications, leveraging XAML for consistency and abstractions, and performance considerations like retained vs immediate mode rendering. The goal is to provide guidance on architecting robust and maintainable WPF applications.
More Related Content
Similar to Architecting WPF Applications (20)
Architecting WPF Applications
- 1. Architecting WPF ApplicationsPaul StovellSenior ConsultantWPF Technical SpecialistReadify
- 3. AgendaWPF OverviewInductive vs. Deductive UINavigationPresentation PatternsCompositionInter-view CommunicationDependency InjectionPartitioningLeveraging XAMLPerformance Considerations
- 4. WPF Overview
- 6. Web or Windows?WindowsIntranet InternetSilverlightWindows FormsJavaJava AppletsASP.NETWPF XBAPWPFAJAX
- 7. XBAP
- 8. XBAP
- 9. WPF Releases.NET Framework 3.0.NET Framework 3.5.NET Framework 3.5 Service Pack 1.NET Framework 4.0
- 11. Deductive UI
- 12. Deductive UI
- 13. Inductive UI
- 14. Inductive UI
- 15. Inductive vs. DeductiveWhy does it matter?UI composition PatternsNavigation PatternsService LayerChangeAddress vs. SaveCustomer
- 16. DataGrid
- 17. Navigation
- 18. Linked ListPage 1Page 2Page 4Page 3
- 19. Centralized DecisionsNavigation HandlerPage 1Page 2Page 3Page 4
- 21. Presentation PatternsModel-View-ViewModelaka Presentation ModelModel-View-Presenteraka Supervising ControllerModel-View-Controller
- 22. Model View ViewModelChange Address ViewModelCustomerAddressAccountsChange Address ViewModel
- 23. Model View ViewModel (Wrapped)View ModelChange Address ViewCustomer VMAccount VMAddress VMChange Address ViewModelModelCustomerAccountAddress
- 24. Model View PresenterChange Address ViewModelCustomerIChangeAddressViewAddressAccountsChange Address Presenter
- 25. Model View Presenter with VMChange Address ViewModelCustomerChange Address ViewModelIChangeAddressViewAddressAccountsChange Address PresenterStateBehaviour
- 26. Model View ControllerControllerView 1Model 1View 2Nav RequestModel 2View 3Model 3
- 27. Presentation PatternsThings to consider:Does every view need separated presentation?Does every view need to follow the same pattern?Code Behind isn’t Evil (DataGrids are)MVPoo
- 28. UI Composition
- 29. Model-based CompositionRecent Orders ViewModelSearch ViewModelWeather ViewModelOrder ListSearchWeather
- 30. UI-based CompositionBottom-UpOrder ListTop Region2. PlaceNavigationBottom Region1. ResolveSearchWeather
- 31. UI-based CompositionTop-DownOrder ListTop RegionBottom RegionSearchWeather
- 33. Inter-View CommunicationStandard .NET eventsSearch ModelChild model raises eventParent model forwards eventResults ModelCriteria Model
- 34. Inter-View CommunicationEvent AggregatorResults ModelCriteria ModelhubPublishHandlePublishHandleAdvert ModelRecent Searches Model
- 35. Event AggregatorAdvantages:Automatic thread switchingWeak eventsHook for cross-cutting concerns
- 38. Partitioning
- 39. PartitioningSplitting partitions:By SKUBy featureBy teamBy department
- 40. PartitioningManaging partitions:With solutionsWith projectsWith assemblies
- 42. PartitioningAlso consider:Deployment and patchingInter-partition dependenciesDev time vs. build time partitioning
- 43. PartitioningRemember: assemblies are like waternecessary for life……but too much can kill you!
- 44. Leveraging XAML
- 45. Abstractions<Grid> <..> <Label Grid.Row="0" Grid.Column="0" Content="First Name:" Target="{Binding ElementName=FirstNameTextBox}" /> <TextBoxGrid.Row="0" Grid.Column="1" Name="FirstNameTextBox" Text="{Binding Path=FirstName}" /></Grid><Form> <Field For="{Binding Path=FirstName}" /> <Field For="{Binding Path=LastName}" /> <Field For="{Binding Path=EmailAddress}" /></Form>
- 46. Consistency<TextBlock Foreground="Red" Text="Please enter..." /><TextBlock Foreground="{StaticResourceColor.Bad}" Text="Please enter..." />
- 47. Style Catalogues<TextBox Width="300" .../><TextBox Width="156" .../><TextBox Width="215" .../><TextBox Style="{StaticResourceTextBox.Big}" /><TextBox Style="{StaticResourceTextBox.Small}" /><TextBox Style="{StaticResourceTextBox.Medium}" />
- 48. BehavioursConsider this:Developers don't write code; they build tools for designers
- 50. Performance ConsiderationsRetained scene vs. Immediate ModeVirtualization (data and UI)Memory leaksThird party componentsPerformance test from day 1