-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Use top level program for the Worker template #33853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Timing seemed appropriate with other discussions going on. I'd love to see the Worker as a top-level. I like this. |
I'd like to see the template further simplified with global usings (like in the websdk). |
src/ProjectTemplates/Web.ProjectTemplates/content/Worker-CSharp/Program.cs
Outdated
Show resolved
Hide resolved
I think we want to do this for all of the templates as well. |
…p/Program.cs Co-authored-by: David Fowler <[email protected]>
FYI @DamianEdwards since he's updating templates right now. I'm okay merging this as is and letting Damian make any additional changes in his PR |
Yep we're in the process of updating all the templates now, see #33947 |
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: - #33853
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: - dotnet#33853
Reduce the Worker template by half, using top level statements.
/cc @bradygaster and @shirhatti