Fix/playground composition build#16199
Open
anuagragith wants to merge 3 commits into
Open
Conversation
- Add missing 'Global' line to playground-composition.sln that caused autolink to corrupt the solution file (MSB5010) - Update SampleCustomComponent path to node_modules and remove ProjectSection to prevent autolink from adding duplicate entries (MSB5004) - Exclude @react-native-picker/picker from autolinking when targeting composition, as it is a UWP/Paper component incompatible with Win32/WinAppSDK (WindowsAppSDK transitive dependency error) - Use $(DefaultPlatformToolset) instead of hardcoded v143 in Playground-Composition.vcxproj and SampleCustomComponent.vcxproj for forward compatibility with newer VS versions Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Align ProjectReference in Playground-Composition.vcxproj to use the same node_modules path as the .sln, preventing parallel build collisions when MSBuild resolves the same project via two different paths (C1041/FTK1011) - Add /FS flag to SampleCustomComponent for synchronized PDB writes - Disable RestoreLockedMode for playground-composition local dev builds to prevent NU1004 errors from stale lock files Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Performance Test ResultsBranch: ✅ Passed161 scenario(s) across 28 suite(s) — no regressionsSectionList
FlatList
TouchableOpacity
ScrollView
TouchableHighlight
Pressable
Modal
Image
ActivityIndicator
Switch
Button
TextInput
View
Text
SectionList.native-perf-test.ts
FlatList.native-perf-test.ts
TouchableHighlight.native-perf-test.ts
TouchableOpacity.native-perf-test.ts
Pressable.native-perf-test.ts
ScrollView.native-perf-test.ts
ActivityIndicator.native-perf-test.ts
TextInput.native-perf-test.ts
Switch.native-perf-test.ts
Button.native-perf-test.ts
Modal.native-perf-test.ts
Image.native-perf-test.ts
View.native-perf-test.ts
Text.native-perf-test.ts
|
Contributor
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
@microsoft-github-policy-service agree company="Microsoft" |
vmoroz
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Type of Change
Summary
I did a fresh git clone, and the playground app was not building or running. I used AI tools to help resolve the issue and am sending out this PR with the fixes. I understand that some of the changes are related to the recent VS Code version updates.
Why
The playground-composition app cannot be built or run locally using npx react-native run-windows from the packages/playground folder. Multiple issues in the solution file, project references, and build configuration cause cascading build failures. These affect anyone cloning the repo and attempting to run the composition playground.
Resolves - building and running the playground app locally
What
Screenshots
No UI changes
Testing
Verified npx react-native run-windows from packages/playground:
Changelog
Should this change be included in the release notes: no
Internal tooling/playground fix — does not affect published packages or end-user functionality.
Microsoft Reviewers: Open in CodeFlow