.net - can enregistrement gratuit COM s'appliquer à une DLL ? -Débordement de pile

At the moment I have something like this for a registration-free COM setup:

• a.exe (depends on b.dll; does not directly depend on c.dll)


• a.exe.manifest (declares registration-free COM registration for c.dll)


• b.dll (depends on c.dll. For example, a .NET TMBIMP generated COM wrapper)


• c.dll (some COM implementation DLL)


• c.dll.manifest (registration-free COM manifest for c.dll)

Is it possible to change this scheme such that the manifest that is on a.exe is instead placed on b.dll? I'd like other programs to be able to reference b.dll without having to add additional manifests everywhere if possible.

(a.exe.manifest has this content:

  <file name="msdia110.dll">
    <comClass description="Debug Information Accessor" clsid="{761D3BCD-1304-41D5-94E8-EAC54E4AC172}" threadingModel = "Both"/>
  </file>

)

and c.dll.manifest was generated using the manifest tool mt.exe. (and is far too long to include here)

At the moment I have something like this for a registration-free COM setup:

• a.exe (depends on b.dll; does not directly depend on c.dll)


• a.exe.manifest (declares registration-free COM registration for c.dll)


• b.dll (depends on c.dll. For example, a .NET TMBIMP generated COM wrapper)


• c.dll (some COM implementation DLL)


• c.dll.manifest (registration-free COM manifest for c.dll)

Is it possible to change this scheme such that the manifest that is on a.exe is instead placed on b.dll? I'd like other programs to be able to reference b.dll without having to add additional manifests everywhere if possible.

(a.exe.manifest has this content:

  <file name="msdia110.dll">
    <comClass description="Debug Information Accessor" clsid="{761D3BCD-1304-41D5-94E8-EAC54E4AC172}" threadingModel = "Both"/>
  </file>

)

and c.dll.manifest was generated using the manifest tool mt.exe. (and is far too long to include here)

Source