Proposal: UseMauiCommunityToolkit MSBuild property for implicit package references

[adem1414]

Proposal

Add an MSBuild property <UseMauiCommunityToolkit>true</UseMauiCommunityToolkit> that automatically injects CommunityToolkit.Maui package references, similar to how <UseMaui>true</UseMaui> works for core MAUI packages.

Motivation

Current approach requires explicit PackageReference declarations:

<ItemGroup>
  <PackageReference Include="CommunityToolkit.Maui" Version="7.0.1" />
  <PackageReference Include="CommunityToolkit.Maui.Markup" Version="4.0.0" />
</ItemGroup>

# This creates:

    Version drift across multiple projects in a solution
    Boilerplate in every .csproj
    Inconsistency with .NET MAUI SDK conventions

# Proposed Implementation
Create a separate SDK package CommunityToolkit.Maui.Sdk that:

    Defines the UseMauiCommunityToolkit MSBuild property
    When true, conditionally injects PackageReference items with aligned versions
    Follows the same pattern as Microsoft.NET.Sdk.Maui

# Example usage:
<PropertyGroup>
  <UseMaui>true</UseMaui>
  <UseMauiCommunityToolkit>true</UseMauiCommunityToolkit>
</PropertyGroup>

# Technical Considerations

    Should this be opt-in or default behavior?
    How to handle version alignment with the installed MAUI workload?
    Should it support selective inclusion (e.g., only Markup, not full toolkit)?

# Alternatives

    Directory.Packages.props (centralized versions but still explicit references)
    Custom .props/.targets files (manual setup per solution)

[pictos]

I don't think that can be done on our end. UseMaui works because of the integration with Project.Sdk styles from Microsoft