A manifest is a set of meta-information about your application. Manifests are important when it comes to getting your application visually themed, and more important still in the brave new world of NT6 and User account Control. If you're using a flavour of VS.Net, they directly support manifest resources. But what if you're stuck using VC6? Fortunately, there is a way that VC6 can be persuaded to apply a manifest.
First of all, create your manifest file. This is simply an XML text file. You can find one online, or use this very simplistic one:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity name="MyApplicationName" processorArchitecture="x86" version="184.108.40.206" type="win32"/> <description> My System </description> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="220.127.116.11" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"/> </dependentAssembly> </dependency> </assembly>
Remember to change the MyApplicationName and My System entries to something more appropriate. It's not strictly necessary for theming purposes, but doubtless Windows will have its own future traps waiting if you don't. Now go to your project resources, select Insert~Resource from the menu, and press the custom button. When you're asked for a resource type, enter 24. Insert the XML given above into the resource, then rename the resource to have the ID 1. I also change the stored filename to manifest.xxx, just to make it obvious what's going on.
Now rebuild your application, and you have a manifest resource. If your application wasn't themed before, it should be now.