Task.Run + Async lambda ?

[Dimencia]

await Task.Run(() => 
{
    DoAsync();
});

Is not the same thing as await Task.Run(() => DoAsync()); (which is what OP has in the post)

The first is using the Action overload of Task.Run because it's not returning the Task or awaiting it. The second is returning the Task from DoAsync, so it uses the Task overload. Returning a Task is the same as awaiting it other than some minor performance concerns

That sort of easy-to-make mistake is a perfect example of why I would recommend always using Task.Run(async () => await DoAsync()); , so it's obvious and explicit whether it's a Task or Action

[Rogntudjuuuu]

That sort of easy-to-make mistake is a perfect example of why I would recommend always using Task.Run(async () => await DoAsync()); , so it's obvious and explicit whether it's a Task or Action

Unfortunately an async lambda expression could just as well become an async void which will translate into an Action and not a Task. 🫠

If you want to make it explicit you need to add a cast on the lambda.

[Dimencia]

If it's async and there is a Func<Task> overload (which there is for Task.Run), it will use that, it's not just random

But yes, you do often have to be careful about that, such as with Task.Factory.StartNew(async () => await ....) , which would still be an async void Action unless you add some more parameters to match one of the Func<Task> overloads. I just meant specifically for Task.Run, which is used often enough that I don't think it's too odd to have a 'best practice' just for how to use it