Skip to content

Conversation

@mink-ms
Copy link
Contributor

@mink-ms mink-ms commented May 22, 2025

If a consumer wants to use both UWPNET and WinUI3, the DLL names conflict since they're both "CommunityToolkit.WinUI.Lottie.dll". So rename the UWPNET one to CommunityToolkit.Uwp.Lottie.dll.

<CsWinRTComponent>true</CsWinRTComponent> prevents the renaming, and it's not required for C# consumers so drop this as well.

<OutputType>winmdobj</OutputType>


<AssemblyName>CommunityToolkit.WinUI.Lottie</AssemblyName>
Copy link
Collaborator

Choose a reason for hiding this comment

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

should it be Uwp here as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

to match UwpNET yes, but this was already WinUI and I only really need the UwpNET one to have a different assembly name so I opted to keep this as-is. Could still switch to Uwp though

Copy link
Collaborator

Choose a reason for hiding this comment

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

Ah I see, then it is ok, let's keep it like that for now, to not change the namespace for the package that is already there.

@aborziak-ms aborziak-ms merged commit 56dcfb8 into main May 22, 2025
5 checks passed
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