> > So given all this, and articles read on MSDN Magazine (which is now > wrong), do you have a proposal or work-around for this? >
Yes - I posted 2 different solutions to this list[1,2]. To read the entire thread (probably a good idea if you haven't already), search for subject = "Bad mojo". BTW - as I mention in the thread, this issue is specific to Delegate.BeginInvoke, not Control.BeginInvoke. I haven't found any similar assertion about Control.BeginInvoke requiring a call to Control.EndInvoke, and an inspection of the implementation of Control.Begin/EndInvoke doesn't make it appear that not calling Control.EndInvoke would be harmful. But that doesn't mean it's officially okay, so YMMV. -Mike DevelopMentor http://staff.develop.com/woodring [1] http://discuss.develop.com/archives/wa.exe?A2=ind0302B&L=ADVANCED-DOTNET &P=R1085&I=-3 [2] http://discuss.develop.com/archives/wa.exe?A2=ind0302B&L=ADVANCED-DOTNET &P=R3960&I=-3
