vb6 “regfreecom” autocreate manifest for ocx file

Question

I think I need to create a manifest file for MSCOMCTL.ocx to use in my VB6 application (reg free)
I will also need to update/create the .res file Then I will need to use M

Answer 1

Here is the entry from the manifest file from one of the VB6 apps I maintain:

<assemblyIdentity name="name of application" processorArchitecture="X86" type="win32" version="a.b.c.d" />

...

<file name="tabctl32.ocx">
    <typelib tlbid="{BDC217C8-ED16-11CD-956C-0000C04E4C0A}" version="1.1" flags="control,hasdiskimage" helpdir="" />
    <comClass clsid="{BDC217C5-ED16-11CD-956C-0000C04E4C0A}" tlbid="{BDC217C8-ED16-11CD-956C-0000C04E4C0A}" progid="TabDlg.SSTab.1" threadingModel="Apartment" miscStatus="" miscStatusContent="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,simpleframe,setclientsitefirst">
        <progid>TabDlg.SSTab</progid>
    </comClass>
    <comClass clsid="{942085FD-8AEE-465F-ADD7-5E7AA28F8C14}" tlbid="{BDC217C8-ED16-11CD-956C-0000C04E4C0A}" threadingModel="Apartment" miscStatus="" miscStatusContent="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,simpleframe,setclientsitefirst" />
</file>

generated from OCS version 6.1.98.39 using https://github.com/wqweto/UMMM using a INI configuration file line like so:

File tabctl32.ocx

This is somewhat different from the one in the question:

• Has a relative path to the file

• Different list of classes

• Various different attributes

Hard to say without experimentation how important those differences might be.

I highly recommend logging your program in Process Monitor and seeing what if any errors you get in the log. This is usually how I identify tricky manifest problems.