-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Release WindowsCommunityToolkit 7.1.3 for Winui 3. #4895
-
Hello,
When is the Winui 3 release 7.1.3 going to be released? There are some changes and fixes that would be very helpful and which we are very waiting for.
Beta Was this translation helpful? Give feedback.
All reactions
Hey @DmitriMilokhov , we are currently in the process of moving components of the Toolkit to our new infrastructure and repo here: https://github.com/CommunityToolkit/Windows
This allows us to have a single code base and to be able to move away from having multiple branches/forks on the Toolkit for UWP, WinUI and Uno. More info on that here: https://devblogs.microsoft.com/ifdef-windows/the-windows-community-toolkit-2023-update/
As you can see, not everything is ported yet to the new repo - but for the stuff that is there, you can already use those packages in your UWP or WinUI app by looking for these pre-release packages on the preview feed. Some for new components that are part of Toolk...
Replies: 2 comments 18 replies
-
Hey @DmitriMilokhov , we are currently in the process of moving components of the Toolkit to our new infrastructure and repo here: https://github.com/CommunityToolkit/Windows
This allows us to have a single code base and to be able to move away from having multiple branches/forks on the Toolkit for UWP, WinUI and Uno. More info on that here: https://devblogs.microsoft.com/ifdef-windows/the-windows-community-toolkit-2023-update/
As you can see, not everything is ported yet to the new repo - but for the stuff that is there, you can already use those packages in your UWP or WinUI app by looking for these pre-release packages on the preview feed. Some for new components that are part of Toolkit Labs: https://github.com/CommunityToolkit/Labs-Windows
Are there specific things that are part of Toolkit 7.13 (for UWP) that you'd need in WinUI? I can then check if that is already ported over or prioritize it if not. Let me know!
Beta Was this translation helpful? Give feedback.
All reactions
-
@niels9001 DropShadowPanel, WrapPanel, WrapLayout, DockPanel, InAppNotification
Beta Was this translation helpful? Give feedback.
All reactions
-
@DmitriMilokhov WrapPanel/WrapLayout are in the Primitives package. DropShadowPanel has already been replaced with the Attached Shadows available in the Extensions or Media packages. And InAppNotification is replaced with the StackedNotificationBehavior on top of InfoBar. That's still in https://aka.ms/toolkit/labs/windows, but we'll be bringing it over to the new Windows repo soon as well as part of the all-up Behaviors package.
Beta Was this translation helpful? Give feedback.
All reactions
-
@michael-hawker even if to use Primitives (submodule of controls) package and Media and then to add tokenizingTB package then the issue is still present (note that the version is still 0.0.1 on nuget)
image
Beta Was this translation helpful? Give feedback.
All reactions
-
@DmitriMilokhov we didn't remove the old 0.0.1 package, but the new preview packages correctly versioned from 8.0 are available: https://dev.azure.com/dotnet/CommunityToolkit/_artifacts/feed/CommunityToolkit-MainLatest/NuGet/CommunityToolkit.WinUI.Controls.TokenizingTextBox/overview/8.0.230803-preview
However, as Niels hinted at, 8.x and 7.x versions of the toolkit are incompatible, you can't mix and match packages across the versions. If you want the latest changes for TokenizingTextBox then you need to update your DeveloperTools, Primitives, and Media package references as well to the new 8.0 versions on the same feed. The Notifications should be independent, but won't get an 8.0 release, it's been supplanted by the Windows App SDK APIs themselves as part of the platform now.
Beta Was this translation helpful? Give feedback.
All reactions
-
Actually it (TokenizingTextBox 8.0.230803-preview) compatible and works without update of the rest of packages. I just did not know that this one in prerelease. Now the issue has been fixed. Thank you.
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
@niels9001 @michael-hawker CommunityToolkit.WinUI.UI.Media.AcrylicBrush will always crash on WinUI3 if switching to .net 8.0, will you investigate this issue and maybe release a new version for WinUI3 on 7.1.X? We could not switch to CommunityToolkit 8.X because lots of controls missing.
Exception: System.Reflection.TargetInvocationException
Message: Exception has been thrown by the target of an invocation.
StackTrace:
at System.RuntimeType.CreateInstanceOfT()
at System.Activator.CreateInstance[T]()
at WinRT.WeakLazy`1.get_Value()
at WinRT.ActivationFactory`1.ActivateInstance[I]()
at Microsoft.Graphics.Canvas.Effects.GaussianBlurEffect..ctor()
at CommunityToolkit.WinUI.UI.Media.Pipelines.PipelineBuilder.<>c__DisplayClass13_0.<<Blur>g__Factory|0>d.MoveNext()
--- End of stack trace from previous location ---
at CommunityToolkit.WinUI.UI.Media.Pipelines.PipelineBuilder.BuildAsync()
at CommunityToolkit.WinUI.UI.Media.XamlCompositionEffectBrushBase.OnConnected()
at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state)
at Microsoft.UI.Dispatching.DispatcherQueueSynchronizationContext.<>c__DisplayClass2_0.<Post>b__0()
Beta Was this translation helpful? Give feedback.
All reactions
-
There was an issue with the migration for the compositor in the Media package, we released 8.0.240109 yesterday which addresses that issue for updating to the 8.0 packages. For any new issues with that package, please file them in the new repo, thanks!
Beta Was this translation helpful? Give feedback.
All reactions
-
Solution: #4963 (comment)
Beta Was this translation helpful? Give feedback.