I personally worked my whole career towards the fact, that if someone knows me and receives a PR from me, it has my name on it. This comes with a certain level of guarantee that I'm quite proud of. Quality of craftsmanship if you will.

This is one of the most valuable things I have attained.

It's funny that vs for Mac is still on thumbnail

Have a safe trip

Can you create the UI ins xaml or everything is android ui?

Have a safe trip. Hope to see you around

Se isso for real, o que eu quero q o Corinthians rebaixe não tá escrito

Bateu até sdds de comer Lamen xD

You can await on the result, using the deferral approach, but it will work only if you're the implementor of event handler

www.pedrolamas.com/2017/04/04/a...

In your case wrapping the caller inside a try/catch should be enough

You can use this nuget and look into the source code to learn more

github.com/TheCodeTrave....

I'll see if I can find more resources on that subject.

Extending... If you don't await the task it will just throw if it has early argument validation, like LINQ does.
The async/await machinery is very similar to the IEnumerable one

I would say this is already solved. You can wrap the code inside your async void with try/catch or use that FireAndForget extension. You can find a lot of them on github. But if it's fire and forget why care about logging the exception?
If you don't await the task, it wouldn't throw

What a beautiful view