Deploy TeeChart ActiveX 8 OCX using Registration-free COM

TeeChart for ActiveX, COM and ASP
Post Reply
PS Soluções
Newbie
Newbie
Posts: 11
Joined: Fri Jun 06, 2008 12:00 am
Location: Brazil
Contact:

Deploy TeeChart ActiveX 8 OCX using Registration-free COM

Post by PS Soluções » Thu Mar 31, 2016 8:01 pm

Hi, I've been trying to deploy my application with TeeChart ActiveX without registering the OCX.

I seems Microsoft lets you deploy the OCX in the same folder as your application and through a .manifest file, it is possible to use the OCX without registration.

I have tried several tutorials and tools and can't make it work. My application is based on .NET 2.0 but uses TeeChart ActiveX.

Is there any limitation I am not aware? Is this kind of deploy possible? If so, please check my manifest files.
myapp deployoment.zip
Manifests
(12.36 KiB) Downloaded 956 times
Thanks.

Reference:

http://stackoverflow.com/questions/4658 ... n-free-com
https://msdn.microsoft.com/en-us/librar ... 2147217396

Marc
Site Admin
Site Admin
Posts: 1209
Joined: Thu Oct 16, 2003 4:00 am
Location: Girona
Contact:

Re: Deploy TeeChart ActiveX 8 OCX using Registration-free COM

Post by Marc » Wed Apr 13, 2016 4:58 pm

Hello,

Apologies for the delay with this reply. We are unfamiliar with use of this technique to call the TeeChart ocx and have been unable to get it to work so far.

The manifest seems to checkout ok in syntax though that may not mean that it's able to do what is required.
checked via:

Code: Select all

mt.exe -manifest TeeChart8.ocx.manifest -validate_manifest
We were unable to build a manifest using mt.exe from teechart8.ocx.

We haven't been to move beyond this error message:
Component 'TeeChart8.ocx' or one of its dependencies not correctly registered: a file is missing or invalid
As a cross-check we tried to provoke an expected error. By changing the assemblyIdentity's name between the executable's "<dependentAssembly><assemblyIdentity.." tag and the ocx's "<assemblyIdentity..." so that they are different, it should have provoked this error message:
Component identity found in manifest does not match the identity of the component requested.
(reference information here: https://msdn.microsoft.com/en-us/librar ... 2147217396)

but the original error message remained, suggesting that the lookup process is not taking place.

It may be that the version of Windows on which we tested it doesn't support the technique (Windows 10). We're not completely finished with checks, we can try a few more things but that's where we're at so far .. ie. no significant progress.

Regards,
Marc Meumann

Post Reply