Geek Answers Handbook

Deploy the COM registration manifest in the C-DLL with your own / managed environment

I am currently working on a mixed proprietary / managed application chain that uses COM without registration. The following figure shows the following:

com

The C # DLL wrapper was created using the tlbimp.exe utility. This allows each of the C # executable files to access its own types and methods in the COM library. The COM library itself uses the server-based RegFree COM manifest.

Everything works fine when RegFree COM client registries are embedded in C # executables. However, I would like to move and unify these manifest files in the C # DLL, which would greatly facilitate the maintenance and synchronization of version information.

Visual Studio #, , DLL (mt.exe). , , # DLL , mt:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"><assemblyIdentity name="FirstClient" version="1.0.0.0" processorArchitecture="msil"></assemblyIdentity><file name="FirstClient.dll" hashalg="SHA1"></file>
<dependency>
            <dependentAssembly>
                        <assemblyIdentity type="win32" name="atl" version="1.0.0.0"></assemblyIdentity>
            </dependentAssembly>
</dependency>
</assembly>

, COM factory, COM-.

-, ? .

+4
1

, . Hans Passant .

+1

More articles:


All Articles