Enable InternalsVisibleTo for CommunityToolkit.Maui.Core

[brminnick]

Description of Change

The .NET MAUI Community Toolkit recently added a new CSPROJ, CommunityToolkit.Maui.Core.

This PR builds on the previous pull request enabling InternalsVisibleTo for the .NET MAUI Toolkit, adding [assembly: InternalsVisibleTo("CommunityToolkit.Maui.Core")].

Additions made

Adds InternalsVisibleTo for the .NET MAUI Community Toolkit libraries

[assembly: InternalsVisibleTo("CommunityToolkit.Maui")]
[assembly: InternalsVisibleTo("CommunityToolkit.Maui.Core")]
[assembly: InternalsVisibleTo("CommunityToolkit.Maui.UnitTests")]
[assembly: InternalsVisibleTo("CommunityToolkit.Maui.Markup")]
[assembly: InternalsVisibleTo("CommunityToolkit.Maui.Markup.UnitTests")]

[maxkoshevoi]

You can also do it via csproj / props files (starting VS 2022):

<ItemGroup>
    <InternalsVisibleTo Include="CommunityToolkit.Maui.Core" />
</ItemGroup>

[VladislavAntonyuk]

You can also do it via csproj / props files (starting VS 2022):

<ItemGroup>
    <InternalsVisibleTo Include="CommunityToolkit.Maui.Core" />
</ItemGroup>

I think we should follow the rule where all other attributes defined

[maxkoshevoi]

You can also do it via csproj / props files (starting VS 2022):

<ItemGroup>
    <InternalsVisibleTo Include="CommunityToolkit.Maui.Core" />
</ItemGroup>

I think we should follow the rule where all other attributes defined

You can move all attributes to props / csproj files. All such attributes were moved from AssemblyInfo.cs to project files with .Net Core, and now InternalsVisibleTo can also be moved there.
For example, you no longer specify version, or author in AssemblyInfo, right?

PS: Also you can add cool stuff like <InternalsVisibleTo Include="$(AssemblyName).UnitTests"/> to Directory.Build.props

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).