the answer to the meaning of life and everything else is

— Control.CheckForIllegalCrossThreadCalls = False —

Well, it is if youre converting Visual Basic .NET projects from Visual Studio 2003 to Visual Studio 2005. With the new .NET frameworks tighter control over cross thread controls calls, Visual Studio 2005 builds automatically throw errors on any cross thread calls that your old multi-thread applications perform – meaning a majority of your previously no problem software all of a sudden break down in a pretty annoying manner. However, thanks to the nifty little call above, your problems are solved – even if it seems like a cheap work around :)