Check Variety Of Topics Related To The Global Digital Transformation.

ASP.NET Marketing Every business needs a solid marketing plan in order to thrive

Microsoft launched .NET Community Toolkit 8.0 after many previews, almost one year after it released v7.1 of its predecessor, Windows Community Toolkit.

This Microsoft-maintained .NET Foundation project is a collection of New interface utilities and APIs that are useful for all .NET developers since none of the APIs are runtime or framework dependent, and its libraries may target .NET Standard 2.0 to .NET 6. 

It is one of the numerous comparable toolkits that are often sets of extra overhead, unique controls, and app services designed to build and show simple developer jobs for many kinds of applications.

The comparatively new toolkit comprises a number of .NET-specific libraries that were separated from the Windows Community Toolkit and placed in their own devoted GitHub repository hence the 8.0 designation, picking up from where the Windows kit versioning was at the time of the split. These libraries include MVVM, High – speed and Diagnostics, and Standard Rescuers.

What Is MVVM Toolkit?

The toolkit’s most significant new feature, according to Redmond, is an improved version of the MVVM (model-view-view-model) Toolkit.

Following a preview period that started in January, the .NET Community Toolkit 8.0.0, a spin-off of the Windows Community Toolkit, was launched on August 4.

Features

• One special characteristic of the release is the addition of new MVVM source generators, which were updated in Preview 1 of the main toolkit, to the last primary component pertaining to the Model-ViewModel-View software design pattern, which separates UI code from back-end or core business logic. 
• These source generators, which decrease the amount of boilerplate code necessary to build an MVVM-based application, now perform more quickly, have simpler commands, more observable property attributes, and a modification to the ViewModel structure to work around C #s of multiple inheritance support.
• Other noteworthy features for source generators and other MVVM components include support for cancellation of commands, broadcast change support for produced properties, ViewModel composition, increased messenger APIs, and redesigned collection APIs.

Sample App for the MVVM Toolkit

The development team revealed a new MVVM Toolkit Sample App, accessible through the Microsoft store, as v8.0 became wide availability.

ASP.NET Marketing Every business needs a solid marketing plan in order to thrive

The variety of functions that are offered to developers are demonstrated by this sample app. It includes documentation and samples for many components. The product description is provided.

In the announcement post, more details are given: – It contains all of the content accessible on MS Docs, along with interactive examples for many of the different APIs.

It’s designed to be a companion for the MVVM Toolkit, and we think it will make this library easier to understand for new users!”

Improved Diagnostics APIs

Using the new interpolated string handler and caller argument expression capabilities of C# 10, the diagnostics libraries, meanwhile, have received some updates.

According to a post on the Microsoft Developer Network, Several Guard APIs that previously approved a string also take a custom handler, allowing Callsites to fully avoid the interpolation phase if no exception is triggered.

.NET 6 support

The newest version of the .NET Community Toolkit adds .NET 6 as a new target to all of the libraries that are currently in use.

       Advantages

• For all libraries, trimming support is now available. This is supported by the fact that all packages have complete trimming observations for all APIs, ensuring that all code is either linker-friendly or explicitly displaying the proper warnings at compile time.
• Nint and nuint are now supported by the HighPerformance package’s CountT>() extension.
• When using .NET 6, more optimizations have been added to all packages.

Final Words

Microsoft launched .NET Community Toolkit 8.0 after many previews, almost one year after it released v7.1 of its predecessor, Windows Community Toolkit. The comparatively new toolkit comprises a number of .NET-specific libraries that were separated from the Windows Community Toolkit and placed in their own devoted GitHub repository hence the 8.0 designation, picking up from where the Windows kit versioning was at the time of the split.