page_type | languages | products | description | urlFragment | ||||
---|---|---|---|---|---|---|---|---|
sample |
|
|
These are some samples to demonstrate the usage of WinUI 3 |
update-this-to-unique-url-stub |
These are some samples to demonstrate the usage of WinUI 3
Ensure that your development computer has Windows 10, version 1803 (build 17134), or a later version installed. WinUI 3 for desktop apps requires 1803 or a later OS version.
Install Visual Studio 2019, version 16.7 Preview 1. You can download this from Visual Studio Preview.
You must include the following workloads when installing the Visual Studio Preview:
- .NET Desktop Development
- Universal Windows Platform development
To build C++ apps you must also include the following workloads:
- Desktop development with C++
- The C++ (v142) Universal Windows Platform tools optional component for the Universal Windows Platform workload
Install both x64 and x86 versions of .NET 5 Preview 4:
- x64: https://aka.ms/dotnet/net5/preview4/Sdk/dotnet-sdk-win-x64.exe
- x86: https://aka.ms/dotnet/net5/preview4/Sdk/dotnet-sdk-win-x86.exe
To access the WinUI 3.0 Preview 1 and project templates, go to https://aka.ms/winui3/previewdownload
Download the Visual Studio Extension (.vsix
) to add the WinUI project templates and NuGget package to Visual Studio 2019 and install it. After installing the .vsix
extension you can load these samples.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.