Windows Community Toolkit v8.0.230907 #228
Replies: 9 comments 13 replies
-
|
Just upgraded, pretty smooth! Thanks for the release. Something I noticed during migration, there are two
and
They appear to be identical (duplicate file?). Only |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @DominicMaas this may have been a leftover oversight in the migration between the .NET Community Toolkit spinning out of the Windows Community Toolkit... 🤦♂️ @Sergio0694 do you remember? Were we supposed to update the Windows one to use the .NET one and forgot when we ported? |
Beta Was this translation helpful? Give feedback.
-
|
There's a known issue with the sample app not displaying XAML/C# code correctly for some reason, we think it's a build authoring issue, but not sure, we're still investigating. Please bear with us! |
Beta Was this translation helpful? Give feedback.
-
|
Following this here - #230 |
Beta Was this translation helpful? Give feedback.
-
|
This is fixed in the store app in Sample App Version 8.0.2. If you have this version and still see problems, let us know. |
Beta Was this translation helpful? Give feedback.
-
|
Happy to see this project is still alive! |
Beta Was this translation helpful? Give feedback.
-
|
I can't find the SystemInformation class in the 8.0 packages from Microsoft.Toolkit.Uwp.Helpers. Is it not available in the new version? There were convenient properties IsFirstRun, IsAppUpdated, etc. I also can't find Print Helper. It's not even in the Toolkit Gallery app( |
Beta Was this translation helpful? Give feedback.
-
|
ImageEx and Carousel were also lost. I didn't see the information about their removal in the description of the deleted components. Is their absence planned, or did they not get into the package by mistake? |
Beta Was this translation helpful? Give feedback.
-
|
There's a lot of code in the toolkit, we're also a small team, so there's only so much that we could do for this release and we had to make a lot of hard decisions. There are not many folks that are contributing to maintain many of these components either. We're happy to work with anyone who wants to help update and modernize any components that it still makes sense to have in the Toolkit. Some like Others like |
Beta Was this translation helpful? Give feedback.
-
|
@michael-hawker I actually checked out the repo and tried to build/run it earlier today. Without luck - I didn't even find a .sln file to open the solution in Visual Studio. There's also no guidance on how to open the project in the Readme. If you are hoping for the community to help, then it might be worth considering to make onboarding easier. |
Beta Was this translation helpful? Give feedback.
-
|
@tipa because of our submodule for shared infrastructure we use Building the whole sample app should be working (as we released our sample app to the store), though individual components can have issues #169 that we're still investigating that make them a bit more difficult out-of-the-box. For your specific issue, if you could share more details on the errors you're seeing (maybe in a new issue?); we're in the process of updating our guidance and wiki to ensure it's easy for anyone to build and contribute to the project. That's why we made simple stand-alone components that can be opened and worked on without having to build the whole toolkit and encapsulate the source, samples, docs, and tests together. |
Beta Was this translation helpful? Give feedback.
-
|
Where is Carousel control? |
Beta Was this translation helpful? Give feedback.
-
|
Let's move the discussion over to CommunityToolkit/Labs-Windows#498 |
Beta Was this translation helpful? Give feedback.
-
|
I see that ListDetailsView is not included in this release. Are there plans to include it later, or suggestion/example how to replace it? |
Beta Was this translation helpful? Give feedback.
-
|
@michael-hawker could you please help clarify it? |
Beta Was this translation helpful? Give feedback.
-
|
Only just noticed this, I need to make a list of all the things missing and cross-reference it so I know when I can safely migrate some apps across. Couldn't see reference to this one in the list either. |
Beta Was this translation helpful? Give feedback.
-
|
I too use the ListDetailsView and ListDetailsViewState. If this has been deprecated, are there any tutorials on how to replace it with something similar? |
Beta Was this translation helpful? Give feedback.
-
|
Hello Looking forward at migration to the new WinUI packages since the 7.1.x was long overdue an update. The legacy packages contained some generic implementations of Settings/File storage, namely: ApplicationDataStorageHelper, which implements a set of interfaces from "CommunityToolkit.Common" Are there plans to have some built in support going forward? Or should applications roll their own implementation for both Packaged/Unpackaged WinUI apps? |
Beta Was this translation helpful? Give feedback.
-
|
The community has been driving an effort around a Storage abstraction in Labs, find more info here. |
Beta Was this translation helpful? Give feedback.
-
|
For the projects using DataGrid, is it recommended to keeping using the 7.X version until it is available in 8.X version? Will 7.X version keep maintain for any security/reliability bug fixing? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, DataGrid is isolated and should continue to work as the 7.x version alongside any other 8.x components. There are no current plans to service the component, our old pipelines for the old WindowsCommunityToolkit repo are non-functional; So, if we needed to, it'd make sense to migrate it to our new shared infrastructure instead. If anyone has interest in owning that sort of effort, please let us know. Our current plan has been to sync and coordinate with the platform on their efforts around a TableView component. Thanks! |
Beta Was this translation helpful? Give feedback.
-
See More Information in Release Blog Here
New Package Structure & Breaking Changes 🚨
If you've been following our previous blogs, you know we've made changes to how namespaces and packages work with 8.0.
We've restructured many packages for a few reasons, but the main benefit is it allows developers targeting or migrating between multiple platforms to easily migrate code written on 8.0 without having to change their source. It also enables library developers to multi-target components with XAML easily.
One namespace to rule them all 💍
Regardless of which new features and packages you use (see below), the namespaces for code within the packages are now unified with a root of
CommunityToolkit.WinUI.*. This ensures that if you target multiple platforms or migrate between them, no code referencing the Toolkit needs to change (just the package)!Package Naming 📦
Previously, starting with 7.x, UWP packages started with
Microsoft.Toolkit.Uwp.UI.*and had similar namespaces, and WindowsAppSDK package started wihCommunityToolkit.WinUI.UI.*and had a similar namespace. See this blog for more information on our package identity journey. These packages will be deprecated and point to their 8.0 equivalents (continue reading).There are now two sets of packages for each component:
CommunityToolkit.Uwp.*for UWP + WinUI 2 or Uno.UICommunityToolkit.WinUI.*for Windows App SDK + WinUI 3 or Uno.WinUIRegardless of the package chosen, as mentioned above, all namespaces have converged on
CommunityToolkit.WinUI.*(note the dropping of the additional.UI.in namespace and package names).If you're using Uno Platform, the same package can be used across your various platform heads now! Just be sure to select the package that corresponds to the target of your Windows platform head, either
.Uwp.or.WinUI.for the Windows App SDK corresponding toUno.UIandUno.WinUI, respectively.Removed Features 🦴
The Toolkit is huge! It's had a lot of features added over the course of the last 7 years. Unfortunately, this means we couldn't migrate everything in this initial transition. Also, some features may not be available on all platforms due to platform limitations or unimplemented APIs.
Our initial focus has been on UWP and Windows App SDK compatibility, followed by Web Assembly (WASM). If you find an issue on a particular platform, please let us know, but we may defer you to the underlying platform's repository if an API is missing.
If there's a feature from the Toolkit that wasn't migrated (and not listed below), open a discussion to garner support for future migration or to get information on contributing to migrate it for everyone.
The following is a partial list of known things which are not included in this release:
ExtensionsandMediapackage.StackedNotificationsBehaviorin ourBehaviorspackage to build on top of the platformInfoBarcontrol.MenuBar.Migration Notes 🚚
Be sure to read the rest of the breaking change notes above! 😉
Most UI controls have their own package now under
CommunityToolkit.<Uwp|WinUI>.Controls.*; we're working to have a meta package again, but do not have one at this time.For individual grouped control packages of 7.x, you can find the following changes:
DropShadowPanelhas been replaced with Attached Shadows in theExtensionsandMediapackages.InAppNotificationis now theStackedNotificationsBehaviorfor WinUI'sInfoBarin theBehaviorspackage.Menuis part of WinUI now, seeMenuBar.RadialProgressBaris part of WinUI'sProgressRingnow, IsIndeterminate="False".Expanderis part of WinUI now.GridSplitteris part of theSizerspackage, it's also been entirely re-written, but with defaults should look/behave the same, if not better!HeaderedControlspackage,HeaderedItemsControlnow usesItemsPresenter'sHeaderandFooternew,Orientationhas been removed, customize theItemsPanelinstead.Uwp/WinUIandUwp/WinUI.UIpackages, look for ourCollections,Converters,Extensions,Helpers, andTriggerspackages.Other controls either have their own package or have not been migrated yet. Search and then open a discussion if you need assistance.
Packages/Feature Overview 📦
Search for either
CommunityToolkit.UwporCommunityToolkit.WinUI(Windows App SDK), depending on your target platform, and one of the packages listed below should appear. Today's release is version8.0.230907.CommunityToolkit.WinUI.Controlsnamespace (see above):'✨' denotes new or updated packages/features from version 7.1.
'🎨' denotes updated XAML styling from version 7.1.
'💻' denotes packages which only target UWP/WindowsAppSDK. However, its absence does not imply that every feature will work across all platforms (see note in introduction).
🔥🐉 Note: Mixing and matching these new 8.0 packages with existing Windows Community Toolkit 7.x packages, especially UI controls, can lead to issues with the namespace changes and dependencies on common code (like the Visual Tree extensions). If there's something that we haven't yet ported but you need, open a discussion to let us know or claim it and contribute!
What's Changed since pre-releases
Full Changelog: v8.0.230828-rc...v8.0.230907
This discussion was created from the release v8.0.230907.
Beta Was this translation helpful? Give feedback.
All reactions