Fixed 3 AppLifeCycle .sln files to unblock PREFast scanning (b#48663282, b#48663490, b#48663652) #324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Although these 3 .sln files built fine in the pipeline, they failed to build when PREFast was enabled, with error like this:
2>C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(320,5): error MSB3779: The processor architecture of the project being built "Any CPU" is not supported by the referenced SDK "Microsoft.VCLibs.Desktop, Version=14.0". Please consider changing the targeted processor architecture of your project (in Visual Studio this can be done through the Configuration Manager) to one of the architectures supported by the SDK: "x86, x64, ARM, ARM64". [F:\_work\1\s\WindowsAppSDK-Samples\Samples\AppLifecycle\Activation\cpp\cpp-win32-packaged\CppWinMainActivationPkg\CppWinMainActivationPkg.wapproj]
In addition, when these solution files were loaded into VS, there was an error message at the top prompting the user to "fix this solution using the Configuration Manager".
These 3 .sln files are updated in this PR to match that in Samples\Notifications\Push\cpp-console-packaged, because it is a comparable sample app which did not trigger PREFast failure.
How built:
How tested:
Target Release
Ideally 1.5+. Might be ok for older releases.
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.