C# proxy generated classes require message pumping I was innocently doing some web services related development in C# using the proxy classes generated from WSDL, when I noticed some strange behavior for processing of web services calls. I was observing that during a section of code that tightly looped (on the UI thread), all processing of web services calls (on a background thread) would block until I executed a statement that would allow for message pumping ('lock' in my case). What a waste of 2 hours to find out what the problem was. What an even bigger waste that I have to introduce message pumping within my tight loop (System.Windows.Forms.Application.DoEvents) to allow the web services calls to process.
1:45:29 PM
|