Question

How can I get this error from with in the DownloadStringCompleted Event? Doesn’t that mean, it’s finished? Is there another event I can fire this from?

I get this error extremely rarely, but once in a while it will happen on my WP7 phone. I have a web client that I fire over and over, and I fire it again from the completed event. Is this happening because there is still some stale connection open? Is there a way to prevent this 100%?

I have checked to see if there is a chance for the thread to walk over itself, but it is only fired from within the completed event.

How can I be sure, when the complete event is fired, the client is no longer isBusy? One suggestion was to add a while with a thread sleep while the client is busy.

Some pseudo code.

var client = new WebClient("URL 1");
client.CompletedEvent += CompletedEvent;
client.downloadasync();

void CompletedEvent(){
Dosomestuff;
client.downloadasync(); //This is where we break.
}

Answer 1

The WebClient only supports a single operations, it cannot download multiple files. You haven’t shown your code, but my guess is that you are somehow firing a new request before the old is completed. My bet is that WebClient.IsBusy is true when you attempt to perform another fetch.

See the following thread:

wb.DownloadFileAsync throw "WebClient does not support concurrent I/O operations." exception