MAUI Dependencies cause issues when updating the MAUI workload with 3rd party dependencies

Description

The issue was first reported by @rdavisau in the SponsorConnect Discord. After updating to MAUI SR1 a project with 3rd party dependencies built against MAUI GA caused a NuGet Dependency downgrade that broke the build. This seems to be caused by a NuGet dependency which is added to libraries which have UseMaui. As discussed with @Redth these dependencies probably shouldn’t be added to NuGet packages built against MAUI

NuGet Dependencies that are automatically added

Resulting error after updating to SR1

Reproduction: https://github.com/rdavisau/maybe-update-maui

Steps to Reproduce

1. Create a MAUI app
2. Add Community Packages that were built against the MAUI GA
3. Use SR1

Version with bug

6.0 (current)

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android, Windows, macOS, Other (Tizen, Linux, etc. not supported by Microsoft directly)

Affected platform versions

all

Did you find any workaround?

No response

Relevant log output

No response

[Redth]

For now here’s a workaround you can use in your library projects to rebuild them without containing the dependency. Add this to your library project which you are packaging into a nuget:

<ItemGroup>
	<PackageReference Include="Microsoft.Maui.Dependencies" Version="$(MauiVersion)">
		<PrivateAssets>All</PrivateAssets>
	</PackageReference>
	<PackageReference Include="Microsoft.Maui.Extensions" Version="$(MauiVersion)">
		<PrivateAssets>All</PrivateAssets>
	</PackageReference>
</ItemGroup>

[Redth]

What seems to be happening here is the Microsoft.Maui.Dependencies and Microsoft.Maui.Extensions are flowing through in dotnet pack of libraries using UseMaui when they really should not be.

Looking into how we can 1) work around this, and 2) fix this behaviour going forward…