>I would strongly advise against using EnableVisualStyles as it has some very nasty side-effects, espceially in applications that use multiple threads or ActiveX controls (like the Web browser control).
>
>It's better to use a Manifest file with the same name as the EXE file, but with an .Manifest extension:
>
>WebMonitor.exe
>WebMonitor.exe.manifest
>
>

><?xml version="1.0" encoding="UTF-8" standalone="yes"?>
><assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
><assemblyIdentity
>   version="1.0.0.0"
>   processorArchitecture="X86"
>   name="Microsoft.Winweb.WebMonitor"
>   type="win32"
>/>
><description>West Wind Web Monitor</description>
><dependency>
>   <dependentAssembly>
>     <assemblyIdentity
>       type="win32"
>       name="Microsoft.Windows.Common-Controls"
>       version="6.0.0.0"
>       processorArchitecture="X86"
>       publicKeyToken="6595b64144ccf1df"
>       language="*"
>     />
>   </dependentAssembly>
></dependency>
></assembly>
>

>
>Note that the names and versions of the assemblies here really don't matter as long as the dependency is in there. In fact you can probably take this file as is and use it. Make sure to store it as UTF-8 encoded text if you paste into notepad.
>
>This provides reliable themes without any side-effects.

When I comment the two lines I have added in the Main() function and add this file in the EXE directory, I end up with those errors when I try to run the EXE:

'DefaultDomain': Loaded 'c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll', No symbols loaded.
'Mitchell': Loaded 'D:\Visual Studio Projects\Mitchell Web Service Monitoring\bin\Mitchell.exe', Symbols loaded.
'Mitchell.exe': Loaded 'c:\windows\assembly\gac\system.windows.forms\1.0.5000.0__b77a5c561934e089\system.windows.forms.dll', No symbols loaded.
'Mitchell.exe': Loaded 'c:\windows\assembly\gac\system\1.0.5000.0__b77a5c561934e089\system.dll', No symbols loaded.
The program '[2712] Mitchell.exe' has exited with code 0 (0x0).