So basically let’s start a small sample app for testing purposes... we'll toss ctList on a form there and call our app ctListTest.exe   Add a couple of node items in the firstdraw and build your app.Now let’s copy our ctList.ocx

to a folderin your app path called bin. We are then going to create a file called ctListTest.exe.manifest in the same folder as the executable. You can also check out some articles on building the manifests into the executables,

here are a couple of command line utilities available from Microsoft that will handle this, but for our example we are going to use the "deploy with executable" method. The XML is going to look like so...

 
<?xml version="1.0" encoding="utf-8"?>

<assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <assemblyIdentity name="ctDate.exe" version="1.0.0.0" type="win32" />

  <file name="bin\ctDate.ocx" asmv2:size="118784">

    <typelib tlbid="{F5A21BA6-2C08-11D5-A85D-0080C8DFC881}" version="6.0" helpdir="" resourceid="0" flags="HASDISKIMAGE"  />

    <comClass clsid="{F5A21BA6-2C08-11D5-A85D-0080C8DFC881}" threadingModel="Apartment" tlbid="{F5A21BA6-2C08-11D5-A85D-0080C8DFC881}" progid="ctDATE.ctDateCtrl.6" description="ctDate Control" />

  </file>

</assembly>

Now you can see we have a single <file> tag in our XML, you can have as many as you need to define for your app. Notice this one is for ctDate, we are going to mod it for use with ctList by changing the tag properties as follows...

This info is from the actual exe file properties...

-orig-<assemblyIdentity name="ctDate.exe" version="1.0.0.0" type="win32" />

-new-<assemblyIdentity name="ctListTest.exe" version="1.0.0.0" type="win32" />

Now for the OCX part...

-orig-

  <file name="bin\ctDate.ocx" asmv2:size="118784">

    <typelib tlbid="{F5A21BA6-2C08-11D5-A85D-0080C8DFC881}" version="6.0" helpdir="" resourceid="0" flags="HASDISKIMAGE"  />

    <comClass clsid="{F5A21BA6-2C08-11D5-A85D-0080C8DFC881}" threadingModel="Apartment" tlbid="{F5A21BA6-2C08-11D5-A85D-0080C8DFC881}" progid="ctDATE.ctDateCtrl.6" description="ctDate Control" />

  </file>

-new-

  <file name="bin\ctList.ocx" asmv2:size="471040">

    <typelib tlbid="{38EC7E50-6A01-4727-88E7-47788ABD54FE}" version="6.0" helpdir="" resourceid="0" flags="HASDISKIMAGE"  />

    <comClass clsid="{2B447B04-4CDC-4F52-915C-694DDCAD79F4}" threadingModel="Apartment" tlbid="{38EC7E50-6A01-4727-88E7-47788ABD54FE}" progid="ctLIST.ctListCtrl.6" description="ctList Control 6.0" />

  </file>

So your XML text for the ctList will be...

<?xml version="1.0" encoding="utf-8"?>

<assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<assemblyIdentity name="ctListTest.exe" version="1.0.0.0" type="win32" />

  <file name="bin\ctList.ocx" asmv2:size="471040">

    <typelib tlbid="{38EC7E50-6A01-4727-88E7-47788ABD54FE}" version="8.0" helpdir="" resourceid="0" flags="HASDISKIMAGE"  />

    <comClass clsid="{2B447B04-4CDC-4F52-915C-694DDCAD79F4}" threadingModel="Apartment" tlbid="{38EC7E50-6A01-4727-88E7-47788ABD54FE}" progid="ctLIST.ctListCtrl.8" description="ctList Control 8.0" />

  </file>

</assembly>

full view

If you wish to test this on your dev machine, you'll have to regsvr32/u ctList.ocx  (in your Studio Controls for COM install folder) then if you did everything right your app should run as normal, rename the ctListTest.exe.manifest to something else and run it and you should get a class unregistered error.

As always from all of us here in support, take care and have a great day!