microsoft / microsoft/WindowsAppSDK-Samples
A mix of Windows SDK's are needed to build the samples
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 335
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 8
Description
The requirements for building the samples says that you need "Windows SDK version 2004 (build 19041) or later. ". Which isn't really true; certain samples require specific Windows SDKs. For example, samples\AppLifecycle\Activation\cpp\cpp-win32-unpackaged\CppWinMainActivation\CppWinMainActivation.vcxproj requires 10.0.22000.0 (which is actually out of support), and there's a good number that fail to build if 10.0.19041 isn't installed.
Given that customers should be using a recent Windows SDK, could the samples all snap forward to, say, 10.0.26100.0?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the requirements text and the named samples\AppLifecycle\Activation\cpp\cpp-win32-unpackaged\CppWinMainActivation\CppWinMainActivation.vcxproj. Inspect the sample project files for inconsistent Windows SDK versions, then verify that the samples build with Windows SDK 10.0.26100.0 and that the requirements accurately describe the needed SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100