Repository navigation
Use non-generic RefreshAsync in samples when they move to CSLA 11 #4961
Description
#1766 (PR #4960) makes the XAML ViewModelBase<T>.RefreshAsync<F>(Func<Task<T?>>) overload obsolete, because its F type parameter was never used. Use RefreshAsync(Func<Task<T?>>) instead.
The samples pin published CSLA 10 packages, which have only the generic overload, so they can't switch yet. When the samples are moved to CSLA 11, replace these calls:
Samples/AvaloniaExample/CslaAvaloniaExample/Views/PersonEditPage.axaml.csSamples/AvaloniaExample/CslaAvaloniaExample/Views/PersonListPage.axaml.csSamples/MauiExample/MauiExample/Pages/PersonEditPage.xaml.cs(2 calls)Samples/MauiExample/MauiExample/Pages/PersonListPage.xaml.csSamples/SimpleNTier/WpfUI/OrderVm.csSamples/WpfExample/WpfExample/Pages/PersonEditPage.xaml.csSupport/Templates/content/CslaWpf-CSharp/Wpf/Pages/PersonEditPage.xaml.cs
Also review the XAML samples for other behavior changes from #1766:
SaveAsyncandRefreshAsynccapture exceptions inException/ViewModelErrorTextinstead of throwing.- On MAUI and Avalonia,
ManageObjectLifetimenow defaults totrue.
Activity
rockfordlhotka commentedon Oct 19, 2026
From the review of #4960: when the samples move to CSLA 11, these pages also need a change, because
SaveAsyncno longer throws.Samples/MauiExample/MauiExample/Pages/PersonEditPage.xaml.csandSamples/AvaloniaExample/CslaAvaloniaExample/Views/PersonEditPage.axaml.csnavigate away afterawait vm.SaveAsync(). After a failed or invalid save they would now leave the page, and the user's edits would be lost without any message. Checkvm.Exceptionandvm.ViewModelErrorTextbefore navigating. The upgrade doc has a before/after snippet.Samples/SimpleNTier/WpfUI/OrderVm.cswrapsSaveAsyncin atry/catchthat no longer fires. HandleError, or checkExceptionafterwards.