I'm currently writing a C# console app that generates a number of URLs that point to different images on a web site and then downloads as byte streams using WebClient.DownloadDataAsync()
.
My issue is that once the first asynchronous call is made, the console app considers the program to be completed and terminates before the asynchronous call can return. By using a Console.Read()
I can force the console to stay open but this doesn't seem like very good design. Furthermore if the user hits enter during the process (while the console is waiting for input) the program will terminate.
Is there a better way to prevent the console from closing while I am waiting for an asynchronous call to return?
Edit: the calls are asynchronous because I am providing a status indicator via the console to the user while the downloads take place.
If that is all your application is doing, I would suggest leaving out the async call; you specifically want the app to 'hang' until the download is complete, so using an async operation is contrary to what you want here, especially in a console app.
Yes. Use a ManualResetEvent, and have the async callback call
event.Set()
. If the Main routine blocks onevent.WaitOne()
, it won't exit until the async code completes.The basic pseudo-code would look like:
Another option is to just call an async Main method and wait on the task returned.
Since .NET 4.5 you can now call
GetAwaiter().GetResult()
What is the difference between .Wait() vs .GetAwaiter().GetResult()?
It should be stated that in C# 7.1
Main
can now be marked asasync
.