WPF provides access to 2D and 3D graphics, controls, and rich document viewing with a consistent programming model. It uses hardware acceleration for improved visual rendering. Key benefits include broad integration, resolution independence, and declarative programming using XAML. The core WPF assemblies include PresentationFramework, PresentationCore, and WindowsBase. The Application class manages the lifetime of a WPF application, while the Window class represents individual windows. Controls such as buttons, text boxes, and containers are used to build the user interface.

1. WPF Deep DiveAniruddha ChakrabartiSr. Solution Architect“If I have six hours to chop down a tree, I will use four hours to sharpen the axe” – Abraham Lincoln

2. Key benefits of WPFBroad integrationProvides access to normal 2D graphics, controls, 3D, video, speech and rich document viewing with consistent programming model as well as tight integrationHardware accelerationImproved Visual RenderingRetained mode graphicsVector graphicsResolution independence (Device Independent Graphics)Declarative programming (aka XAML)Rich composition, layout and customizationEasy deploymentIncorporates best of Web and WindowsIntegrate developers and designers

3. WPF Architecture

4. WPF Architecture

5. WPF: Assemblies and NamespacesPrimary Assemblies containing the WPF APIPresentationFrameworkPresentationCoreWindowsBasemilcore (unmanaged)mil: Media Integration LayerNamespacesSystem.WindowsOther child namespaces starting with System.Windows except System.Windows.Forms (Win Forms)System.Windows.ControlsSystem.Windows.DataSystem.Windows.DocumentsSystem.Windows.Media (+ child namespaces)System.Windows.ShapesManagedUnmanaged/Native

6. WPF Base Class HierarchyWindowsBasePresentationFrameworkPresentationCore

7. WPF Base Class DetailsSystem.Threading.DispatcherObject:

8. Provides basic constructs for dealing with concurrency and threading. WPF is based on a messaging system implemented by the dispatcher - works much like familiar Win32 message pump

9. System.Windows.DependencyObject:

10. Provides reach Property System (DP + attached property)

11. System.Windows.Media.Visual:

12. Provides for building a tree of visual objects. Visual is designed to be extremely lightweight and flexible, so most of the features have no public API exposure.

13. Visual is really the entry point to the WPF composition system. Visual is the point of connection between these two subsystems, the managed API and the unmanaged milcore.

14. System.Windows.UIElement:

15. defines core subsystems including Layout, Input, and Events

16. System.Windows.FrameworkElement:

17. Provides Advanced Layout on top of the features provided by UIElement

18. Provides DataBinding & Styles

19. System.Windows.Controls.Control:

20. Provides Templating SupportDifferent type of WPF applicationsStandalone/Desktop Applications

21. Window class is used to create windows and dialog boxes

22. Browser Hosted Applications / XAML Browser Applications (XBAP)

23. Create Page, Page Function

24. Loose XAML pages (can be opened in IE)XAML (eXtensibleApplication Markup Language)

25. XAML OverviewSimple general-purpose, XML based declarative programming language for constructing & initializing .NET objects

26. .NET Framework 3.0 includes

27. A compiler and run-time parser for XAML,

28. Plug-in that enables to view standalone WPF-based XAML files (sometimes called loose XAML pages) inside IE.

29. Can be used independent of WPF (e.g. WF)

30. XAML Spec defines rules that map .NET namespaces, types, properties, and events into XML namespaces, elements, and attributes.

31. Declaring an XML element in XAML (known as an object element) is equivalent to instantiating the corresponding .NET object (always via a default constructor).

32. Setting an attribute on the object element is equivalent to setting a property of the same name (called a property attribute)XAML Example<Windowx:Class="WpfApplication1.Window1"xmlns="http://schemas.microsoft.com/winfx/2006/xaml/ presentation"xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Title="First XAML Example" Height="300" Width="300"> <StackPanel><Button Height="70"FontFamily="Verdana"FontSize="18">Hello World</Button></StackPanel></Window>namespace WpfApplication1{ public partial class Window1 : Window{public Window1(){InitializeComponent();} }}Window1.xaml.csWindow1.xamlButton btn =new Button();btn.Height = 70;btn.FontFamily =new FontFamily("Verdana");btn.FontSize = 18;btn.Content = "Hello World";panel.Children.Add(btn);

33. Loose XAML files<Button xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" Height="50" Width="250" FontSize="16"> Hello from loose XAML page </Button>

34. XAML Namespace<Window x:Class="WpfApplication1.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:w="clr-namespace:WpfApplication1"XAML Namespace

35. Default Namespace: declared with xmlns attribute

36. Xmlns: http://schemas.microsoft.com/winfx/2006/xaml/presentation - maps to .NET namespace System.Windows.Controls.

37. Mapping defined in PresentationFramework.dll assembly [assembly:XmlnsDefinition (“http://schemas.microsoft.com/winfx/2006/xaml/presentation”, “System.Windows.Controls”)]

38. Root object element in a XAML file must specify at least one XML namespace: used to qualify itself & any child elements.

39. Additional XML namespaces (on the root or on children) can be declared , but each one must be given a distinct prefix to be used on any identifiers from that namespace.

40. e.g. WPF XAML files typically use a second namespace with the prefix x (denoted by using xmlns:x instead of just xmlns): xmlns:x=http://schemas.microsoft.com/winfx/2006/xaml (XAML Language namespace) – System.Windows.MarkupXML Properties and Attributes<Button>Hello World <Button.FontSize>16</Button.FontSize></Button><ButtonFontSize="16">Hello World </Button>Attribute SyntaxProperty Element Syntax<Button Width="120">Hello World</Button><Button Width="1.2in">Hello World</Button><Button Width="1.2 IN">Hello World</Button><Button Width="2.8cm">Hello World</Button><Button Width="70pt">Hello World</Button><Button Width="15e-1in">Hello World</Button><Button Width="NaN">Hello World</Button>

41. XamlReader ClassXamlReader class exposes some functionality of XAML Parser

42. Defined in namespace System.Windows.Markup

43. Load & Parse method allows to parse XAML and convert it into initialized objectApplication and Window class

44. Application classApplication object is responsible for

45. Managing the lifetime of the application

46. Tracking the visible windows

47. Dispensing resources

48. Managing the global state of the application

49. Provides Run() method to start an app

50. Most WPF apps create a subclass of Application

51. Run() method starts the dispatcher which sends the messages & events.

52. WPF requires the UI thread to be STA because many components that WPF uses (e.g. Clipboard) require STA

53. The [STAThread] marker on the entry-point function is required like Win Forms and User32First WPF Appusing System;using System.Windows;namespace ConsoleApplication1{ class Program{[STAThread]static void Main(string[]args){Window mainWin =new Window();mainWin.Title ="First WPF App";Application app =new Application();app.Run(mainWin); } }}

54. Using VS2008 WPF Template

55. Important Members of ApplicationProperty

56. Current (static) – refers to current App

57. MainWindow – points to application’s Main window

58. Windows – collection of windows of app

59. StartupUri – Uri of resource to be started if Run is called without parameter

60. ShutdownMode

61. Method

62. Run – starts the app

63. Shutdown – ends the app

64. Events

65. Startup & Exit

66. Activated & Deactivated

67. DispatcherUnhandledExceptionWindowWPF Window provides abstraction for Win32 Window

68. OS does not distinguish between windows with WPF content and normal Win32 content.

69. Similar to Form in Win Forms

70. Represented by System.Windows.Window class

71. Order of Window events1. Constructor is called.2. Window.Initialized event is raised.3. Window.Activated event is raised.134. Window.Loaded event is raised.5. Window.ContentRendered event is raised.6. User interacts with the window.7. Window.Closing event is raised.8. Window.Unloaded event is raised.9. Window.Closed event is raised.

72. Navigation WindowProvides navigation in Windows app (like navigation from one page to another in web Apps)

73. Built with three basic concepts –

74. Navigation Hosts: hosts the content like Browser

75. Navigable Content: Page

76. Journal: responsible for tracking the navigation actions<Label>This is page 1</Label><TextBlock><HyperlinkNavigateUri="Page2.xaml">Go to Page2 </Hyperlink></TextBlock>

77. Controls

78. ControlsProvides standard set of controls like Button, TextBox, CheckBox, ComboBox, RadioButton etc.

79. Provides Content property instead of familiar Win32 Text property. Content can be any object, not only string.

80. Content actually supports both string and UIElement

81. For other datatypes, it uses the string value returned by ToString().

82. Most WPF controls ship with several default appearances

83. Aero (default Windows Vista theme)

84. Luna (default Windows XP theme)

85. Royale (Media Center & Tablet PC theme)

86. Classic (Win 9x theme)

87. Provides different type of controls

88. Content Controls

89. Buttons

90. Simple Containers

91. Containers with a Header

92. Items Controls

93. Range Controls

94. Text and Ink ControlsButtonsProvides Content property - derived from ContentControl base classContent property is of type object (not text), so any content is allowed, not only text.Provides rich composition

95. Simple ContainersLabel – Can be assigned an Access Key, which can be used to set the cursor to the next TextBox.

96. ToolTip – provides rich tooltip like Office 2007

97. Frame – Can contain HTML contentContainers with HeaderGroupBox – Groups other controls. Has Header property.

98. Expander – New control in WPF. Does not exist in Win32/ WinForms.

99. Contains a button that enables you to expand and collapse the inner content.

100. By default, the Expander starts out collapsed.Items ControlComboBox

101. ListBox

102. ListView

103. TabControlCustomizing ComboBoxIsEditable=”False” (default)TextSearch.Text property setIsEditable=”True”

104. Range ControlProgressBarSlider

105. Text and Ink ControlTextBoxRichTextBoxCan Contain Rich formatted text & imagesPasswordBoxInkCanvas

106. OtherMenu, MenuItem

107. ContextMenu

108. ToolBar

109. StatusBar

110. WPF does not provide these control

111. Grid

112. CalendarSizing, Positioning and Transform

113. SizingLayout and size depends on the negotiation between Parent and Child control

114. Input

115. Height & Width property (from FrameworkElement)

116. Avoid Explicit Sizing

117. use MinHeight, MinWidth, MaxHeight & MaxWidth

118. Output

119. ActualHeight, ActualWidth (read only)

120. DesiredSize, RenderSize (UIElement)