DethKnite - 2011-05-03

Duplicate, see Bug #2101354.
With this in mind, I was able to minimalize the issue by adding code that ensured downloads were completed prior to copy.

I added a private _IsSaved bool on the
FileDownloader, and a corresponding public method.
I then set the IsSaved = true; after the
{
lock
{
save file...
}
IsSaved = true;
}

Then in the Updater I added a wait while (!downloader.IsSaved).
I logged this and found that at times the last file was kinda quirky to
the gun. But this is a harsh fix... though it works. I am not sure what is
causing the finished to fire off prematurely.

More info in comments of the bug listed above.