you might try creating a "Registration-Free COM" manifest for TImpLib.exe,
and put your TLB details in that manifest as needed.
You can put the manifest XML into a separate TImpLib.exe.manifest text file
in the same folder as TImpLib.exe.
Thank you, Remy, for helping us to solve the problem.
Registration free COM is widely used within our applications, and since TLibImp has no internal manifest, there is a possibility (as suggested by you), that it might respond to an external manifest.
We tried this, but unfortunately without success. It seems, that TLibImp does not take into account the external manifest info, when trying to resolve references.
In case we used an incorrect external manifest or made other mistakes, I added some details info below.
/Emil
Details:
TLibImp.exe was copied to the directory containing the .tlb files
A TLibImp.exe.manifest file was added in the same directory and with the following content
(Common being the .dll to resolve external references from the .tlb file currently processed):
<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly
manifestVersion="1.0"
xmlns="urn:schemas-microsoft-com:asm.v1"
xmlns:asmv1="urn:schemas-microsoft-com:asm.v1"
xmlns:asmv2="urn:schemas-microsoft-com:asm.v2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity
type="win32"
name="TLibImp"
version="1.0.0.0"
/>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Common"
version="1.0.0.0"
publicKeyToken="" />
</dependentAssembly>
</dependency>
</asmv1:assembly>
Connect with Us