Actually, based on my research, they didn't fix this in .NET v2.0. You still have to do the recommended workarounds they suggest for .NET v1.1 when accessing GUI controls from a thread other than the one that created them in order to avoid random crashing.
I understand why they wouldn't want to default them to be thread safe due to performance concerns (checking thread IDs can be slow). But there's no reason not to have this as a property option on each control. This would keep the developer from having to wrap each and every control into a thread safe wrapper. I haven't seen any mention of whether they have addressed this in .NET v3.0. Eric Wachsmann FlexRadio Systems > -----Original Message----- > From: Jim Lux [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 10, 2006 4:36 PM > To: Eric Wachsmann > Cc: 'Flex-radio Reflector' > Subject: RE: [Flexradio] Vs2003 vis a vis Vista > > At 02:03 PM 10/10/2006, Eric Wachsmann wrote: > >Those are in our source. Look in the root\trunk\Source\Console\Invoke\ > >folder for the definitions. These are basically wrappers on the existing > >GUI controls that incorporate Thread Safe mechanisms. Why this is not a > >defined property on the controls from MS, I'll never understand. It > would > >save many programmers some headaches. > > Tnx > > In most of the .net 2.0 stuff, things are already thread safe. A > better threading model is one of the big advantages of VS2005, tec. > > Jim > _______________________________________________ FlexRadio mailing list FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/ FlexRadio Homepage: http://www.flex-radio.com
