Update Program.cs

[IEvangelist]

I think most of the other top-level programs/templates call Run() instead of await RunAsync(). For the sake of consistency we should probably use Run.

Related to the evolution of templates with .NET 6:

• Use top level program for the Worker template #33853

/cc @DamianEdwards @bradygaster @davidfowl and @shirhatti

[DamianEdwards]

Do we know if there was a specific reason the worker template called RunAsync() already?

[IEvangelist]

Do we know if there was a specific reason the worker template called RunAsync() already?

Hi @DamianEdwards - I'm the one who originally proposed the async version. I personally liked it better, and preferred the explicit usage of asynchrony. While I understand that the Run() does something similar to .ConfigureAwait(false).GetAwaiter().GetResult() and it's "safe" to do so, I still leaned towards liking the async main. I also like that is showcases async and await in top-level programs, which through the perspective of new developers coming to .NET it might be nice for the discoverability.

There was no other reason than my personal preferences and the original PR. For the purpose of consistency however, I think we should use Run instead (even though I prefer RunAsync). Does that make sense?

[mkArtakMSFT]

Thanks @IEvangelist!
@rafikiassumanimsft do you want to sign-off on this too as I believe your team owns the worker template?

[pranavkm]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).