-
Notifications
You must be signed in to change notification settings - Fork 4k
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
async Main with multiple entrypoints #26315
Comments
Closing this issue as no repro, pls revert if it repros with latest VS . |
in case anyone else runs into this ... you can manually add this to your csproj file and get passed this issue
|
VS: 16.5.0 Preview 4.0 Startup object's dropdown-list doesn't work with an |
Confirmed with 2019 16.4.5. @aktxyz's solution sort of works, but when I switch between startup objects it likes to remove the async one. So it works if you're willing to go into the xml and keep pasting it - not a real solution, unfortunately. |
it wouldn't be a good work around without an annoying side effect ... for the longest time I could not figure out why it kept reverting but eventually found what you found |
In Visual Studio 16.9.3 public static async Task Main(string[] args) { Still doesn't show up in the property page and if the csproj is edited to set |
Closing this issue as we've seen no reply to the request for more information. If you are able to get the requested information, please add it to the issue and we will retriage it. |
Fixed with #75808 |
I have three console apps in a project with Main entrypoints. I changed one of them to be "async Task Main". Now, when I go into the project properties, the one that I set to async no longer shows up in the "Startup object" application setting. The two that I left alone still show up.
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/235706/async-main-with-multiple-entrypoints.html
VSTS ticketId: 602403
These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)
The text was updated successfully, but these errors were encountered: