You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
Why you don't throw the error into the Ui thread, like in EventToCommandBehavior?
Why you don't use TaskContinuationOptions.OnlyOnRanToCompletion in ContinueWith?
Why you don't use Device.BeginInvokeOnMainThread for Command.CanExecute and Command.Execute?
Why you don't use ConfigureAwait(false) after ContinueWith, if you use anyway Device.BeginInvokeOnMainThread inside ContinueWith which is executed in the background or UI thread (the thread can be random)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Why you don't throw the error into the Ui thread, like in EventToCommandBehavior?
Why you don't use TaskContinuationOptions.OnlyOnRanToCompletion in ContinueWith?
Why you don't use Device.BeginInvokeOnMainThread for Command.CanExecute and Command.Execute?
Why you don't use ConfigureAwait(false) after ContinueWith, if you use anyway Device.BeginInvokeOnMainThread inside ContinueWith which is executed in the background or UI thread (the thread can be random)?
Beta Was this translation helpful? Give feedback.
All reactions