No VC burden to implement XP style interface

No VC burden to implement XP style interface

In other words, test.exe must first call the initcommoncontrols function (abolished, not recommended) or the initcommoncontrolsex function to register component classes from comctl32.dll. This step is required in VB, but in VC (MFCProgram), We seem to have not called this function, but why can the compiled program still implement the XP style? The reason is that MFC did this for us. If we have the window class registered with MFC, it will call the _ afxinitcommoncontrols function, and the main operation of _ afxinitcommoncontrols is to load comctl32.dll and then judge. is there any initcommoncontrolsex function in the DLL file? If yes, call it. If no, call initcommoncontrols. Some people may look at the name of the window class starting with "afx" like me, so they like to register the window class themselves, however, when registering our own window class, make sure that the initcommoncontrolsex function has been called. Remember that if you forget it, you will see a blank window.

Having said so much, I am a little confused. Now return to the topic. The method I mentioned above is described on many websites, but it has a fatal drawback, that is, it must be included. the manifest file is like a shadow file, and where the EXE file is located, it will be like this. Of course we don't want to see it. Is there a way to "merge" it into the EXE file? The answer is yes, which is exactly the meaning of the word "no burden" in this article.

The hosts file is merged.

First, obtain the. manifest file:

<? XML version = "1.0" encoding = "UTF-8" standalone = "yes"?>
<Assembly
Xmlns = "urn: Schemas-Microsoft-com: ASM. V1"
Manifestversion = "1.0">
<Assemblyidentity
Processorarchitecture = "x86"
Version = "5.1.0.0"
Type = "Win32"
Name = "client.exe"/>
<Description> just for client </description>
<Dependency>
<Dependentassembly>
<Assemblyidentity
Type = "Win32"
Name = "Microsoft. Windows. Common-Controls"
Version = "6.0.0.0"
Publickeytoken = "6595b64144ccf1df"
Language = "*"
Processorarchitecture = "x86"/>
</Dependentassembly>
</Dependency>
</Assembly>

As you can see, this is actually an XML file. Open notepad, copy the above content, save the disk, and the file name is arbitrary. Here I save it as xpstyle. manifest.

Create an MFC Appwizard (exe) project in VC, either document/view or dialog, and then set the xpstyle. copy the manifest file to the project directory, and then use notepad or other text editing tools to manually modify the resource files under the project directory (. RC), add a line at the end of the file:

1 24 "xpstyle. manifest"

Compile and connect the project generation. EXE executable file in vcss and run it.

Is that simple? That's simple. :)

Here I will explain more. The last line added, "1" represents the resource ID, which must be "1 ". "24" indicates the resource type. I think we are very familiar with resources such as rt_accelerator, rt_bitmap, rt_menu, and rt_string. "24" is actually rt_manifest. The last quotation marks will not repeat me.

After compilation, this. EXE file can be obtained anywhere. It is an XP-style interface, and you no longer need to rely on the. manifest file?