What Is WPF?
WPF (Windows Presentation Foundation) is a UI framework Microsoft shipped with .NET Framework 3.0 in 2006 for building Windows desktop applications. Unlike its predecessor Windows Forms, WPF renders its UI through DirectX rather than the older GDI+ layer, giving it hardware-accelerated, vector-based graphics that scale cleanly across different screen resolutions and DPI settings. It measures layout in device-independent units (1/96 inch) instead of raw pixels, so a button defined at a fixed size looks the same physical size on a 96-DPI monitor and a 200% scaled 4K display.
Cricket analogy: Just as a stadium's giant screen re-renders the scoreboard graphics natively for HD and 4K broadcasts instead of just stretching a fixed-pixel image, WPF re-renders its vector UI for each display's DPI instead of scaling a bitmap like GDI+ did in WinForms.
WPF's Rendering Model
WPF renders through a retained-mode visual tree rather than the immediate-mode drawing calls WinForms issued to GDI+. Every on-screen element is a Visual object composed into a tree rooted at UIElement and FrameworkElement, and the composition engine walks that tree each frame, letting DirectX batch and hardware-accelerate the actual drawing. Because the tree persists between frames, WPF only needs to invalidate and redraw the parts that changed instead of the whole window, and it can apply transforms, opacity, and effects to any branch of that tree without extra plumbing.
Cricket analogy: Like the DRS system re-rendering only the disputed part of a delivery — the ball-tracking path — instead of replaying the entire over, WPF's retained visual tree redraws only the branch that changed instead of repainting the whole window on every frame.
Core Building Blocks: XAML, Controls, and Data Binding
WPF applications typically pair a XAML file, which declares the UI tree as markup, with a code-behind class that handles events and initialization logic — MainWindow.xaml and MainWindow.xaml.cs are compiled together into one partial class. Its data binding engine can connect any DependencyProperty on a control to a property on a view-model object, and when that object raises INotifyPropertyChanged, the bound control updates automatically without manual UI-refresh code. Styles, ControlTemplates, and DataTemplates let you restyle or completely replace how a control looks while keeping its behavior, and ResourceDictionaries let those styles be shared or swapped for theming.
Cricket analogy: Like a scorer's manual entry immediately updating the digital scoreboard the moment a run is logged, without the scorer separately walking over to update the display, WPF's data binding pushes view-model changes to the UI automatically via INotifyPropertyChanged.
<!-- MainWindow.xaml -->
<Window x:Class="HelloWpf.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Title="Hello WPF" Height="200" Width="300">
<StackPanel Margin="16">
<TextBlock Text="{Binding Greeting}" FontSize="20"/>
<Button Content="Click Me" Click="OnClick" Margin="0,12,0,0"/>
</StackPanel>
</Window>// MainWindow.xaml.cs
public partial class MainWindow : Window
{
public MainWindow()
{
InitializeComponent();
DataContext = new MainViewModel();
}
private void OnClick(object sender, RoutedEventArgs e)
{
MessageBox.Show("Button clicked!");
}
}WPF ships as part of the Windows Desktop SDK. On modern .NET (.NET 6+), you target it with <UseWPF>true</UseWPF> in your .csproj, and the app still only runs on Windows even though the rest of .NET is cross-platform.
Where WPF Fits Today
WPF remains a mainstay for enterprise line-of-business applications on Windows — trading desks, healthcare records systems, CAD-adjacent tools, and internal engineering apps still rely on it because of its mature data-binding model, rich control set, and years of accumulated tooling like Prism and MVVM Light for structuring large codebases. Since .NET Core 3.0, WPF runs on modern .NET (currently .NET 8/9) rather than being locked to the old .NET Framework, so existing WPF codebases can move onto the current runtime and get performance and tooling improvements without a full UI rewrite.
Cricket analogy: Like a franchise such as Mumbai Indians keeping a core group of experienced players who know the system while still adopting the latest fitness and analytics tools each season, WPF keeps its mature MVVM patterns while now running on modern .NET runtimes.
WPF is Windows-only — there is no supported way to run a WPF app on macOS or Linux. If you need a cross-platform desktop UI on .NET, look at .NET MAUI or Avalonia UI instead.
- WPF is a Windows desktop UI framework introduced in .NET Framework 3.0 (2006), rendering through DirectX instead of GDI+.
- UI is measured in device-independent units (1/96 inch) so layouts scale consistently across DPI settings.
- Rendering uses a retained-mode visual tree, letting WPF redraw only invalidated branches instead of the whole window.
- XAML markup plus a code-behind class define each window or control; both compile into one partial class.
- Data binding connects DependencyProperties to view-model properties and updates automatically via INotifyPropertyChanged.
- Styles, ControlTemplates, and DataTemplates let you restyle controls without changing their behavior.
- Since .NET Core 3.0, WPF runs on modern .NET (.NET 8/9) rather than being locked to .NET Framework, but remains Windows-only.
Practice what you learned
1. Which rendering technology does WPF use to draw its UI, unlike the GDI+-based WinForms?
2. What unit does WPF use for layout measurements?
3. In a standard WPF project, MainWindow.xaml and MainWindow.xaml.cs compile into what?
4. What interface does a view-model implement so bound WPF controls update automatically when a property changes?
5. Since which .NET version can WPF run outside of the legacy .NET Framework?
Was this page helpful?
You May Also Like
WPF vs WinForms
A practical comparison of WPF and Windows Forms covering rendering, UI definition, and data binding to help you choose the right framework.
Project Structure in WPF
How a typical WPF project is organized, from the default App.xaml/MainWindow template files to MVVM folder conventions and resource dictionaries.
XAML Basics in WPF
The fundamentals of XAML syntax in WPF — elements, attributes, layout panels, markup extensions, and attached properties.
Related Reading
Related Study Notes in Microsoft Technologies
Browse all study notesWindows 10 / UWP Development Study Notes
.NET · 30 topics
Microsoft TechnologiesWindows Batch Scripting Study Notes
Batch · 30 topics
Microsoft TechnologiesMFC (Microsoft Foundation Classes) Study Notes
C++ · 30 topics
Microsoft TechnologiesSilverlight Study Notes
.NET · 30 topics
Microsoft TechnologiesXAML Study Notes
.NET · 30 topics
Microsoft TechnologiesMVVM Design Pattern Study Notes
.NET · 30 topics