Bump Microsoft.Toolkit.Uwp.UI.Controls.DataGrid from 6.1.1 to 7.0.0

[dependabot]

Bumps Microsoft.Toolkit.Uwp.UI.Controls.DataGrid from 6.1.1 to 7.0.0.

Release notes

Sourced from Microsoft.Toolkit.Uwp.UI.Controls.DataGrid's releases.

v7.0.0

Packages available on NuGet

Changes:

🐉 Here be Dragons! 🐉 The 7.0.0 release of the Toolkit has a lot of changes, it's our biggest release to date! Be careful when upgrading or following existing documentation as things have moved or changed from the 6.1.1 release. We've made many of these changes to help decrease the dependencies the Toolkit has and reduce the footprint it can have in applications. For our more common scenarios, this can mean a potential reduction of 80-90% that the Toolkit has on your application size.

The main substantial changes are highlighted for you here. More detailed links to specific changes in this release are blow.

Happy coding!

Refactoring Highlights

• The Toolkit's min version is now 1809 (see #3440)
• The Controls packages now rely on WinUI 2.5, therefore you need to follow their getting started guidance as well.
  • RadialProgressBar has been deprecated as the ProgressRing in WinUI now supports determine state.
  • TabView has been removed, please migrate to the WinUI one.
  • HeaderedTextBlock has been removed, please use HeaderedContentControl instead.
  • The custom cache feature built-in to ImageEx was removed, but can be achieved by subclassing the control and overriding a method.
  • The default stretch behavior for VerticalAlignment of WrapPanel has changed to align better with WPF, this will manifest if you have different sized items in your collection, you can add alignment properties to change back to the original top alignment, see issue #3574 for details on this change in behavior. If this effects you significantly, please let us know there.
• The Controls package is now a meta package of other packages, this means you can optimize your app by figuring out which controls you need are in one of the sub-packages. Find out more about this and how to leverage it to optimize your application footprint after development at https://aka.ms/wct/optimize
• The Animations package has been restructured
  • Implicit animations and expression helpers should work as similar, though AnimationCollection is now ImplicitAnimationSet, see more details below in feature highlights
  • The animation helpers that were Behaviors have been removed and replaced with our new Animation system which has helpers for behaviors and effects across the new Microsoft.Toolkit.Uwp.UI.Behaviors and improved Microsoft.Toolkit.Uwp.UI.Media packages to create similar results with more flexibility and customizations. There is also the new UIElementExtensions.VisualFactory which can be used for static effects as these behaviors weren't always for animations.
• The Extensions namespace has been removed so that all extensions are available in the root namespace for their package. See Issue #3422 and PR #3743 for details.
  • The Visual/Logical tree extensions have been refactored to be more explicit in the behavior and provide new functionality, see #3685 for more info.
• DispatcherHelper is now DispatcherQueue extensions, we've provided guidance in the deprecation messages for migration. Performing these changes will help if you plan to move to XAML Islands or WinUI 3 which can only work with DispatcherQueue.
• The Services and Parsers packages have been removed.
  • The only service we'll support moving forward is for the Microsoft Graph, you can find out more about the work we're doing in that space here, these components will be updated at a later date.
  • We recommend other solutions for integration with 3rd-Party services like RestSharp and Refit {.NET Foundation}.
  • We recommend Markdig for parsing Markdown and plan to move to it in the future (see #3200) for our Markdown parsing needs for the MarkdownTextBlock, that code has been internalized into the new Microsoft.Toolkit.Uwp.UI.Controls.Markdown package.
  • See this simple migration doc for moving to the official .NET RSS Parser.
• The StorageHelper serialization story has changed, see #3636. Minimal work is required to maintain compatibility.
• The Deferred event helpers have moved to the Microsoft.Toolkit package.
• The Visual Studio Platform Analyzers have been removed.
• The Diagnostics APIs in Microsoft.Toolkit are now in a separate package Microsoft.Toolkit.Diagnositcs
• The MyGet feeds are no longer valid, if you want to keep up-to-date on the latest builds of the Toolkit, see our Wiki Preview Packages Page
• The Array extensions in Microsoft.Toolkit have moved to the Microsoft.Toolkit.HighPerformance package #3444
• Singleton has been removed, see #3134 for guidance on implementing this pattern
• The Platform Analyzer has been removed, please use the latest Visual Studio version to get the best code analysis experience for your development needs.
• The JavaScript version of the Notifications package has been removed.
• The Win32 XAML Islands packages have not received an update, please see that repo for more details
• The Graph Controls have not been updated yet to align with 7.0.0-preview5 or 7.0.0. We are in the process of continuing to re-work these controls as we gather more feedback from developers and plan an updated release later this year. In the meantime the live samples have been changed to only doc pages in the sample app. Find out more on that repo as we make changes in the open.

Feature Highlights

• MVVM Toolkit, a .NET Standard MVVM Library - docs and samples - By @​Sergio0694
• Whole new fluent C# and XAML Animations! - docs - By @​Sergio0694 #3680
  • We have introduced a whole new way to perform explicit composition animations within XAML and in code-behind docs
  • This can be mixed with Behaviors and Effects! For instance: https://twitter.com/SergioPedri/status/1351879471029219329

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #49.