Description

This adds a new sample called "Simple Island app". The concept of this sample is that it starts with VS's Win32 desktop app template, and adds what's needed to pull in WinAppSDK and put a single island in that app with Xaml content. It uses WinAppSDK as a Framework Package, and is an "unpackaged" app to stay true to the goal of keeping it as much like a vanilla win32 app as possible.

The best way to understand this change is to go commit by commit. The first commit is the blank Win32 project from the VS template. Then we add nuget packages. Then we make our necessary changes to put Xaml onto the app.

Still TODO:

• Add code to make tab navigation work.

Target Release

This sample is for use with WinAppSDK 1.4 and later.

Checklist

TODO: STILL IN PROGRESS

• Samples build and run using the Visual Studio versions listed in the Windows development docs.
• Samples build and run on all supported platforms (x64, x86, ARM64) and configurations (Debug, Release).
• Samples set the minimum supported OS version to Windows 10 version 1809.
• Samples build clean with no warnings or errors.
• [For new samples]: Samples have completed the sample guidelines checklist and follow standardization/naming guidelines.
• If I am onboarding a new feature, then I must have correctly setup a new CI pipeline for my feature with the correct triggers and path filters laid out in the "Onboarding Samples CI Pipeline for new feature" section in samples-guidelines.md.
• I have commented on my PR /azp run SamplesCI-<FeatureName> to have the CI build run on my branch for each of my FeatureName my PR is modifying. This must be done on the latest commit on the PR before merging to ensure the build is up to date and accurate. Warning: the PR will not block automatically if this is not run due to '/azp run' limitation on triggering more than 10 pipelines.