This moves the WinAppSDK Scene Graph (lifted Composition + Input) Microsoft/WindowsCompositionSamples into the WindowsAppSDK-Samples github repo. This will be the new home for these samples going forward, and they will be further integrated into WinAppSDK.
Target Release
(Current Latest) WinAppSDK 1.5
Checklist
[X] Samples build and run using the Visual Studio versions listed in the Windows development docs.
[X] Samples build and run on all supported platforms (x64, x86, ARM64) and configurations (Debug, Release).
[X] Samples set the minimum supported OS version to Windows 10 version 1809.
[X] Samples build clean with no warnings or errors.
[N/A] 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.
[N/A] 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.
Description
This moves the WinAppSDK Scene Graph (lifted Composition + Input) Microsoft/WindowsCompositionSamples into the WindowsAppSDK-Samples github repo. This will be the new home for these samples going forward, and they will be further integrated into WinAppSDK.
Target Release
(Current Latest) WinAppSDK 1.5
Checklist
/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.