Mvvm

Mvvm copied to clipboard

When using the `Get(T value, ...)` and `Set(T value, ...)` methods (which are called possible quite often, each time we read or modify the property), there is a closure allocation...

philfontaine

Fixes #28 I don't see why `Execution.Task` needs to be awaited again, because `Execution.TaskCompleted` was already awaited.

bitbonk

CA1001 is currently supressed.

StephenCleary

Fixes #30 I think it is OK if `OperationCancelledException`s always propagate

bitbonk

Add AsyncCommand<T> with strongly typed parameter

1

### Description In the WPF MVVM world, it is fairly common for projects to write their own simple command implementations, sometimes called DelegateCommand, RelayCommand or simply Command. Since ICommand uses...

adamgauthier

- Made a small refactoring. - Classes `AsyncCommand` & `CustomAsyncCommand` no more sealed. - Create new base class `AsyncCommandBaseExtended` - Added two classes: `CancellableCustomAsyncCommand` & `CancellableAsyncCommand`. They are usefull because...

kirbex

Put up release package on nuget.org

1

Hi Stephen, is there a chance you can put up a version of this package as release version? We have been using Nito.AsyncEx version 4.0 for quite some time and...

pfeigl

The current version `CancelCommand.Wrap()` does not propagate `IsCancelled` information to the `Execution.IsCancelled` of the parent `AsyncCommand`. In the following code public AsyncCommandsDemoViewModel(IDataClient dataClient) { this.CancelGetData = new CancelCommand(); this.GetData =...

bitbonk

The current version of the `AsyncCommand` rethrows any exception that occurs in the task run by the command. In the following code public AsyncCommandsDemoViewModel(IDataClient dataClient) { this.CancelGetData = new CancelCommand();...

bitbonk

How to use AsyncCommand canExecuteChangedFactory?

3

I'm trying to use `pre3` and it seems that I cannot pass a simple function any more as the the second parameter for the AsyncCommand as you have suggested here:...

RedX2501