Repository navigation
Namespace migration and WinUI3 package MicrosoftToolkit.WinUI.Lottie - #500
Conversation
michael-hawker
left a comment
michael-hawker
left a comment
There was a problem hiding this comment.
Couple of comments and info about where we're heading with the WCT.
Also not sure if you've done an audit for Dispatcher usage and XamlRoot for the general migration guidance. If things work in XAML Islands today, you should be fine. But always good to check if you missed a move to DispatcherQueue.
aborziak-ms
changed the title
michael-hawker
left a comment
michael-hawker
left a comment
There was a problem hiding this comment.
Couple of small things I think to sort out how the packages will be created.
| | Target | Branch | Status | Recommended NuGet package | | ||
| | ------ | ------ | ------ | ------ | | ||
| | 7.1.0 release | main | [](https://dev.azure.com/dotnet/WindowsCommunityToolkit/_build/latest?definitionId=61&branchName=main) | [](https://www.nuget.org/packages/CommunityToolkit.WinUI.Lottie/) | | ||
| | 7.1.0 release | main | [](https://dev.azure.com/dotnet/WindowsCommunityToolkit/_build/latest?definitionId=61&branchName=main) | [](https://www.nuget.org/packages/Microsoft.Toolkit.Uwp.UI.Lottie/) | |
There was a problem hiding this comment.
We can clean this up later, as we'll probably want to split out and have NuGet shields for both the UWP and the WinUI packages. For now we can leave as-is and not worry about it until things are published and we have all the actual live links.
michael-hawker
left a comment
michael-hawker
left a comment
There was a problem hiding this comment.
Cool, think things are set now. Just need to try from the DevOps feed and make sure the packages work alright from UWP/WinUI 3 apps!
Added project for WinUI3 package. Since there are a lot of namespaces changes also added preprocessor flag to distinguish WinUI 3 package from UWP package.