MyUniversity
StudyComputer ScienceTracksCertificationsPapers
CommunityDiscussionsLeaderboard
Sign in

Client Apps for .NET Concepts

Desktop and cross-platform client apps in .NET, from MVVM and data binding to choosing between WPF, WinUI, .NET MAUI and Avalonia, explained in depth, one at a time.

Sort

MVVM & Data Binding

1

MVVM and CommunityToolkit.Mvvm

MVVM measured with CommunityToolkit.Mvvm 8.4.2 in a console project (net10.0 and net11.0, macOS): the code the generators write for [ObservableProperty] on partial properties, the exact order of events, async commands and the exception that crashes the app, WeakReferenceMessenger against StrongReferenceMessenger with the GC, Ioc.Default as a service locator and a ViewModel tested with MSTest 4 with no UI. XAML and bindings are docs only, plus where MVVM Light, Prism and ReactiveUI stand today.

Read →

UI Frameworks

1

Choosing a .NET Client UI Framework

A decision guide for where to write a .NET client app today, with support dates and state read from the primary sources (the Windows developer FAQ, the MAUI support policy, the WPF and WinForms what's new pages): WinUI 3, .NET MAUI, WPF, WinForms, Blazor Hybrid and Blazor in the browser, plus Avalonia and Uno in a short table. Measured on macOS arm64 with SDK 10.0.100 and 11.0.100: which client templates exist, what the MAUI workload requires, WPF and WinForms projects that compile but cannot run off Windows, a WPF app hosting Blazor and a Blazor WebAssembly publish, with the rest marked docs only.

Read →

This project is open source.View on GitHubPrivacy

HomeStudyDiscussionsSettings