Getting started with the Windows UI Library
The toolkits are available as NuGet packages that can be added to any new or existing Visual Studio project.
WinUI 2.2 is the latest stable version of WinUI and should be used for apps in production. For information on trying out early previews of WinUI 3.0, see WinUI 3.0 (Alpha).
Download and install the Windows UI Library
Download Visual Studio 2019 and ensure you choose the Universal Windows Platform development Workload in the Visual Studio installer.
Open an existing project, or create a new project using the Blank App template under Visual C# -> Windows -> Universal, or the appropriate template for your language projection.
To use WinUI 2.2, you must set Min version to 15063 or higher and Target version to 18362 or higher in the project properties.
In the Solution Explorer panel, right click on your project name and select Manage NuGet Packages. Select the Browse tab, and search for Microsoft.UI.Xaml or WinUI. Then choose which Windows UI Library NuGet Packages you want to use. The Microsoft.UI.Xaml package contains Fluent controls and features suitable for all apps.
You can optionally check "Include prerelease" to see the latest prerelease versions that include experimental new features.
Add the Windows UI (WinUI) Theme Resources to your App.xaml resources. There are two ways to do this, depending on whether you have additional application resources.
a. If you don't have other application resources, add
<XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls"/>to your Application.Resources:
<Application> <Application.Resources> <XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls" /> </Application.Resources> </Application>
b. Otherwise, if you have more than one set of application resources, add
<XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls"/>to Application.Resources.MergedDictionaries:
<Application> <Application.Resources> <ResourceDictionary> <ResourceDictionary.MergedDictionaries> <XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls" /> </ResourceDictionary.MergedDictionaries> </ResourceDictionary> </Application.Resources> </Application>
The order of resources added to a ResourceDictionary affects the order in which they are applied. The
XamlControlsResourcesdictionary overrides many default resource keys and should therefore be added to
Application.Resourcesfirst so that it doesn't override any other custom styles or resources in your app. For more information on resource loading, see ResourceDictionary and XAML resource references.
Add a reference to the toolkit to XAML pages and your code-behind pages.
In your XAML page, add a reference at the top of your page
In your code (if you want to use the type names without qualifying them), you can add a using directive.
using MUXC = Microsoft.UI.Xaml.Controls;
Additional steps for a C++/WinRT project
When you add a NuGet package to a C++/WinRT project, the tooling generates a set of projection headers in your project's
\Generated Files\winrt folder. To bring those headers files into your project, so that references to those new types resolve, you can go into your precompiled header file (typically
pch.h) and include them. Below is an example that includes the generated header files for the Microsoft.UI.Xaml package.
// pch.h ... #include "winrt/Microsoft.UI.Xaml.Automation.Peers.h" #include "winrt/Microsoft.UI.Xaml.Controls.Primitives.h" #include "winrt/Microsoft.UI.Xaml.Media.h" #include "winrt/Microsoft.UI.Xaml.XamlTypeInfo.h" ...
For a full, step-by-step walkthrough of adding simple support for the Windows UI Library to a C++/WinRT project, see A simple C++/WinRT Windows UI Library example.
Contributing to the Windows UI Library
WinUI is an open source project hosted on GitHub.
We welcome bug reports, feature requests and community code contributions in the Windows UI Library repo.
If you're new to UWP, then we recommend that you visit the Getting Started with UWP Development pages on the Developer portal.