WinUI 3 ships as a component of the Windows App SDK framework package, with Visual Studio project templates in the Windows App SDK Visual Studio Extension (VSIX).

WinUI 2 can be used in UWP applications and incorporated into desktop applications using XAML Islands (for installation instructions, see Getting started with the WinUI 2 Library). WinUI 3 can be used to build production-ready desktop/Win32 Windows apps. UX stack and control library tightly coupled to the OS and Windows SDKs. UX stack and control library completely decoupled from the OS and Windows SDKs, including the core framework, composition, and input layers of the UX stack. WinUI 2, the 2nd generation of WinUI, ships as a standalone NuGet package, and is integrated with Windows SDKs. The following table highlights some of most significant differences between WinUI 3 in the Windows App SDK and WinUI 2 for UWP. The WinUI libraries are hosted in the WinUI GitHub repo where you can file feature requests or bugs, and interact with the WinUI where you can file feature requests or bugs, and interact with the WinUI team. With support for both desktop and UWP apps, you can build with WinUI from the ground up, or gradually migrate your existing MFC, WinForms, or WPF apps using familiar languages such as C++, C#, Visual Basic, and JavaScript (using React Native for Windows).

The Windows UI Library (WinUI) is a native user experience (UX) framework for both Windows desktop and UWP applications.īy incorporating the Fluent Design System into all experiences, controls, and styles, WinUI provides consistent, intuitive, and accessible experiences using the latest user interface (UI) patterns. While both can be used in production-ready apps on Windows 10 and later, each have different development targets. At this time, there are two generations of the Windows UI Library (WinUI): WinUI 2 for UWP and WinUI 3 in the Windows App SDK.

DefenderUI 1.14 for windows download