Split the 9 folders under Samples\AppLifecycle\Activation into corresponding cs (C-sharp) and cpp (C++) subfolders. This is a straightforward change for the purpose of breaking the internal aggregator pipeline artifact for Samples\AppLifecycle\Activation down into 2 parts, cs and cpp, resulting in 2 smaller artifacts. This hopefully would reduce the chance of hitting "Out Of Memory" errors when downloading artifacts to an AzDO pipeline job agent.
The changes to a .vcxproj file are auto updates performed by VS.
Target Release
1.5.
Checklist
Verified on a local machine that the .sln file for a randomly picked cpp sample app can still be built successfully. Repeated this test for a randomly picked cs sample app.
[ ] 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.
[ ] 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.
Description
Split the 9 folders under Samples\AppLifecycle\Activation into corresponding cs (C-sharp) and cpp (C++) subfolders. This is a straightforward change for the purpose of breaking the internal aggregator pipeline artifact for Samples\AppLifecycle\Activation down into 2 parts, cs and cpp, resulting in 2 smaller artifacts. This hopefully would reduce the chance of hitting "Out Of Memory" errors when downloading artifacts to an AzDO pipeline job agent. The changes to a .vcxproj file are auto updates performed by VS.
Target Release
1.5.
Checklist
Verified on a local machine that the .sln file for a randomly picked cpp sample app can still be built successfully. Repeated this test for a randomly picked cs sample app.
/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.