Perhaps it's too late at night, but I can't think of a nice way to do this.
I've started a bunch of asynchronous downloads, and I want to wait until they all complete before the program terminates. This leads me to believe I should increment something when a download starts, and decrement it when it finishes. But then how do I wait until the count is 0 again?
Semaphores sort of work in the opposite way in that you block when there are no resources available, not when they're all available (blocks when count is 0, rather than non-zero).
I had a similar issue where i needed to reset a server upon some event, but had to wait for all the open requests to finish before killing it.
I used the CountdownEvent class upon server start to initialize it with 1, and inside each request I do:
And upon receiving the ResetEvent i signal the counter once to eliminate the starting 1, and wait for live requests to signal they are done.
Basically you initialize the CountdownEvent with one, so that it's in a non signaled state, and with each AddCount call you are increasing the counter, and with each Signal call you are decreasing it, always staying above 1. In your wait thread you first signal it once to decrease the initial 1 value to 0, and if there are no threads running Wail() will immediately stop blocking, but if there are other threads that are still running, the wait thread will wait until they signal. Watch out, once the counter hits 0, all subsequent AddCount calls will throw an exception, you need to Reset the counter first.
In .NET 4 there is a special type for that purpose CountdownEvent.
Or you can build similar thing yourself like this:
For each thread you start Interlock.Increment a counter. And for each callback on thread finish, Decrement it.
Then do a loop with a Thread.Sleep(10) or something until the count reaches zero.
Check out the CountdownLatch class in this magazine article.
Update: now covered by the framework since version 4.0, CountdownEvent class.
Here is my C# 2.0 implementation of CountdownLatch:
Based on the suggestions here, this is what I came up with. In addition to waiting until the count is 0, it will sleep if you spawn too many threads (count > max). Warning: This is not fully tested.