With the .NET Neighborhood Toolkit 8.3 launch, Microsoft stated that APIs throughout all packages have been annotated to completely help trimming and AOT compatibility, to make sure that any a part of the toolkit goes easily even in these eventualities. Additionally within the model 8.3 launch, the MVVM Toolkit provides help for the net8.0-windows10.0.17763.0 goal, to be absolutely trim and AOT-compatible with WinAppSDK (WinUI 3). Including this goal framework ensures that every one sorts that is perhaps marshaled to WinRT could have all the required interop code generated for them, Microsoft stated.
Additionally in model 8.3, there are extra efficiency enhancements for the MVVM toolkit. The main focus was on making help for INotifyPropertyChanging absolutely pay-for-play, Microsoft stated. Thus, when this interface is just not wanted, there might be no extra overhead due to it. When this property is ready to false, all code related to INotifyPropertyChanging in ObservableObject might be trimmed out.
Among the many bug fixes within the replace, a repair has been made to a scenario wherein generated OnPropertyChanging strategies weren’t being invoked for dependent properties when utilizing [NotifyPropertyChangedFor]. And the ObservableValidator.HasError property will not routinely present up in desk views in frameworks that dynamically generate columns from declared properties. Model 8.3 of the .NET Neighborhood Toolkit follows final yr’s 8.2 launch, which additionally introduced new options to MVVM and efficiency enhancements to MVVM supply mills.