Downloaded 224 times
Uploaded byPaul Stovell
Architecting WPF Applications
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
Architecting WPF Applications
- 1. Architecting WPF ApplicationsPaulStovellSenior ConsultantWPF Technical SpecialistReadify
- 3. AgendaWPF OverviewInductive vs.Deductive UINavigationPresentation PatternsCompositionInter-view CommunicationDependency InjectionPartitioningLeveraging XAMLPerformance Considerations
- 4.
- 5.
- 6. Web or Windows?WindowsIntranet InternetSilverlightWindows FormsJavaJava AppletsASP.NETWPF XBAPWPFAJAX
- 7.
- 8.
- 9. WPF Releases.NET Framework3.0.NET Framework 3.5.NET Framework 3.5 Service Pack 1.NET Framework 4.0
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. Inductive vs. DeductiveWhydoes it matter?UI composition PatternsNavigation PatternsService LayerChangeAddress vs. SaveCustomer
- 16.
- 17.
- 18. Linked ListPage 1Page2Page 4Page 3
- 19. Centralized DecisionsNavigation HandlerPage1Page 2Page 3Page 4
- 20.
- 21. Presentation PatternsModel-View-ViewModelaka PresentationModelModel-View-Presenteraka Supervising ControllerModel-View-Controller
- 22. Model View ViewModelChangeAddress ViewModelCustomerAddressAccountsChange Address ViewModel
- 23. Model View ViewModel(Wrapped)View ModelChange Address ViewCustomer VMAccount VMAddress VMChange Address ViewModelModelCustomerAccountAddress
- 24. Model View PresenterChangeAddress ViewModelCustomerIChangeAddressViewAddressAccountsChange Address Presenter
- 25. Model View Presenterwith VMChange Address ViewModelCustomerChange Address ViewModelIChangeAddressViewAddressAccountsChange Address PresenterStateBehaviour
- 26. Model View ControllerControllerView1Model 1View 2Nav RequestModel 2View 3Model 3
- 27. Presentation PatternsThings toconsider:Does every view need separated presentation?Does every view need to follow the same pattern?Code Behind isn’t Evil (DataGrids are)MVPoo
- 28.
- 29. Model-based CompositionRecent OrdersViewModelSearch ViewModelWeather ViewModelOrder ListSearchWeather
- 30. UI-based CompositionBottom-UpOrder ListTopRegion2. PlaceNavigationBottom Region1. ResolveSearchWeather
- 31. UI-based CompositionTop-DownOrder ListTopRegionBottom RegionSearchWeather
- 32.
- 33. Inter-View CommunicationStandard .NETeventsSearch ModelChild model raises eventParent model forwards eventResults ModelCriteria Model
- 34. Inter-View CommunicationEvent AggregatorResultsModelCriteria ModelhubPublishHandlePublishHandleAdvert ModelRecent Searches Model
- 35. Event AggregatorAdvantages:Automatic threadswitchingWeak eventsHook for cross-cutting concerns
- 36.
- 37.
- 38.
- 39. PartitioningSplitting partitions:By SKUByfeatureBy teamBy department
- 40. PartitioningManaging partitions:With solutionsWithprojectsWith assemblies
- 41.
- 42. PartitioningAlso consider:Deployment andpatchingInter-partition dependenciesDev time vs. build time partitioning
- 43. PartitioningRemember: assemblies arelike waternecessary for life……but too much can kill you!
- 44.
- 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'twrite code; they build tools for designers
- 49.
- 50. Performance ConsiderationsRetained scenevs. Immediate ModeVirtualization (data and UI)Memory leaksThird party componentsPerformance test from day 1
- 51.