Skip to content

Conversation

michael-hawker
Copy link
Member

See CommunityToolkit/Windows#587

At least in part, there's many inconsistencies in the Labs packages from changes to templates. Both in inclusion of .Labs. in package as well as .Controls. or not.

Something we should fix in the Labs repo so everything is consistent with how the packages are named (between source, csproj props, and nuget packages).

That will make some of this code obsolete, but should just work, so we can commit here and fix in Labs after so the sample app can be correctly pointing to all packages.

(Note it's hard to copy labs components into the main repo, and vice-versa due to dependencies. We need a method in labs where we reference toolkit components differently so we can just assign properties for project reference vs. package reference, etc... [There may be an issue for that already?])

…imental components

See CommunityToolkit/Windows#587
At least in part, there's many inconsistncies in the Labs packages from changes to templates. Both in inclusion of `.Labs.` in package as well as `.Controls.` or not.
Copy link
Member

@Arlodotexe Arlodotexe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved to keep things moving for 8.2 stable release.

I'll want to make a light note for later; in this PR we've hardcoded something we also have declared in MSBuild (PackageIdPrefix). Someday we may want to consolidate and connect the logic to make this more reusable.

@Arlodotexe Arlodotexe merged commit b70bef7 into main Apr 3, 2025
11 checks passed
@Arlodotexe Arlodotexe deleted the llama/fix-587 branch April 3, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants