Cross Theaded Calls - Many controls Heavy GUI Application after .net 1.1 2.0 upgrade- best way ??

Posted by keepsmilinyaar on Stack Overflow See other posts from Stack Overflow or by keepsmilinyaar
Published on 2010-03-18T17:24:54Z Indexed on 2010/03/18 18:51 UTC
Read the original article Hit count: 287

I have recently upgraded a .net1.1 solution to .net2.0. AS this is a very heavy GUI appilcation with loads of controls and many multithreaded operations that update the GUI. While these operations worked seamlessly in .net1.1 it is throwing up Cross Threaded Illegal operations after the upgrade. Considering the fact that tehre are numerous grids, buttons and status labels that need to be updated via these multi threaded operations, I decided to code for checking the InvokeRequired solution, however doing that for every control would probably not be the best way to go about it.

I was wondering if you could suggest a better way of how I can go about it or propose any OOPS based class structure that I could code around to make the code look better.

Please do let me know if my question is unclear.

Thanks in advance

© Stack Overflow or respective owner

Related posts about cross-thread-communicatio

Related posts about .net-2.0