I have vs2005 final, on a dual processor machine running win 2003 server.
I can report that the ProgressChanged events of the Backgroundworker are
most of the times executed in a random order.
This is counter-logical and not specified in the documentation.
Imagine binding a progressbar and watching it randomly decreasing and
increasing.
Imagine reading a big file, and adding the lines read to a StringBuilder ( I
know is not the recommended method, one can use FileStream.BeginRead ).
I finally used a native window and good oldPostMessage to execute my events
on the main thread.
And voila, no more problems...
|
Similar Threads
