Thanks.

>You can embed it in your EXE using a resource editor like described there, but it's a hassle since it's not automated as you have to add it as a Win32 Resource not a .NET resource.
>
>I just include the manifest file as part of shipping the app...
>
>+++ Rick ---
>
>>I understand how to edit this file. I also found the MSDN help topic titled, "Creating a Manifest for Your Application" at,
>>
>>http://msdn.microsoft.com/library/en-us/xmlsdk/html/xmmscCreatingaManifestForYourApplication.asp
>>
>>What I don't understand is how to revise my project so that the manifest is included automatically when I rebuild my app either to debug it or release it.
>>
>>The MSDN Article says,
>>
>>

add the following line to the header file:
>>
>>CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST "YourApp.exe.manifest"

>>which doesn't seem to make sense to me in a C# project, it seems to be a reference to C++. I suspect that I need to use an attribute.
>>
>>Should I add MyApplication.exe.manifest in the Startup project in my solution and add some kind of attribute or do I need to wait until I have an installer class and include it there? If someone could "supplement" the documentation in MSDN for me, I would appreciate it.
>>
>>>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.
>>>
>>>+++ Rick ---
>>>
>>>
>>>
>>>>>Can I have a XP theme on a form? Is that supported with VS.NET 2003?
>>>>
>>>>You should look at the Application class, EnableVisualStyles method. See the help topic: ms-help://MS.VSCC.2003/MS.MSDNQTR.2003FEB.1033/vbcon/html/vbtskapplyingwindowsxpthemestowindowsformsapplications.htm