Action conventions for async methods

The current conventions are like x:Name="Delete" ==> Binds to methods Delete() and guard property CanDelete.

The guideline for methods with async modifiers is to add an Async suffix to them. For example:

public async Task DeleteAsync()

Now there’s a question: should the convention pick up x:Name="Delete" => DeleteAsync() or should we rename to x:Name="DeleteAsync"?

Also, the convention should accept guard methods which don’t have an Async suffix. For example:

public async Task DeleteAsync();
public bool CanDelete { get; }

per guideline the property should not have an Async suffix because it’s not async.

[BrunoJuchli]

@altso

Methods returning Task are treated by Caliburn.Micro like coroutines. When the Task throws an Exception you’ll be informed by the Coroutine.Completed event. The ResultCompletionEventArgs.Error property will contain the Exception.

[nigel-sampson]

Resolved in #158 still considering changing the behavior of coroutines.