Repository navigation
Aspire.CommunityToolkit.* -> CommunityToolkit.Aspire.* #124
Description
To ensure that we're meeting the governance requirements properly within the Community Toolkit space we need to flip the namespace around.
This will also ensure that we don't hit any problems in the future around ownership.
/cc @michael-hawker
Activity
Moving from Aspire.CommunityToolkit to CommunityToolkit.Aspire
Moving from Aspire.CommunityToolkit to CommunityToolkit.Aspire (#1877)
ErikEJ commentedon Oct 22, 2024
@aaronpowell hoping this will not affect VS visibility?
aaronpowell commentedon Oct 22, 2024
Do you mean via the
Add Aspire Integrationmenu item? That's not reliant on the package naming (still have to work out with the tooling team how we'll get there)michael-hawker commentedon Oct 22, 2024
Thanks @aaronpowell for the chat and discussion on this space. Took some notes on the history/reasoning here for our list of items to ensure we document in central governance: Community Toolkit Organizational Board (view)