News

.NET Community Toolkit v8.0 Preview 3 Tweaks MVVM Source Generators

Microsoft shipped .NET Community Toolkit v8.0 Preview 3 as part of its effort to coalesce all of its general .NET libraries into a one-stop-shop resource.

That resource is the .NET Community Toolkit repo on GitHub, a collection of platform-agnostic helpers and APIs that work for all .NET developers -- maintained and published by Microsoft -- that's part of the .NET Foundation. Its offerings that come via NuGet include successors to the old Windows Community Toolkit and MvvmLlight along with others, with the full gamut being:

It's that first item, the MVVM Toolkit, that sees several tweaks in Preview 3.

An interactive grouped collection of contacts using the MVVM Toolkit collection APIs
[Click on image for larger, animated GIF view.] An interactive grouped collection of contacts using the MVVM Toolkit collection APIs (source: Microsoft).

For example, one improvement to the MVMM Toolkit revamps observable grouped collections, whose functionality is depicted in the animated graphic above.

However, many changes in Preview 3 concern the second item, source generators, a C# compiler feature that lets C# developers inspect user code as it is being compiled and generates new C# source files on the fly that are added to the user's compilation.

Source generator APIs reduce needed boilerplate code when working with MVVM, providing helpers such as observable properties, commands and much more.

MVVM Toolkit source generator tweaks added since Preview 1 in January include:

  • Partial property changed methods: "When using [ObservableProperty] to generate observable properties, the MVVM Toolkit will now also generate two partial methods with no implementations: On<PROPERTY_NAME>Changing and On<PROPERTY_NAME>Changed. These methods can be used to inject additional logic when a property is changed, without the need to fallback to using a manual property."
  • Cancellation support for commands: "A new property has been added to the [ICommand] attribute, which can be used to instruct the source generator to generate a cancel command alongside the original command. This cancel command can be used to cancel the execution of an asynchronous command."
  • Broadcast change support for generated properties: "We've also added a new [AlsoBroadcastChange] attribute which can be used on generated observable property from a type that inherits from ObservableRecipient (or that is annotated with [ObservableRecipient]). Using it will generate a call to the Broadcast method, to send a message to all other subscribed component about the property change that just happened. This can be useful in scenarios where a property change from a viewmodel needs to also be notified to other components in the application."

More details on all of the above and many other new features, improvements and changes -- including breaking changes -- can be found in the changelog and announcement post.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube