Incorrect manifest files of COM reference with Isolated=True

[Ulrich Schumacher]

Hello programmers,

VS 15.8.7 seems to create incorrect manifest files in the following scenario:

- reference a COM dll
- set Isolated=True in reference properties

Now it should be possible to do a xcopy deployment of the solution (so the COM registration is not needed by using this property).

This worked all fine but in our latest release (created with VS 15.8.7 or 15.8.6) an exception is thrown. The application shows the same behaviour as if the property was set to Isolated=False (COM not found).

By analysing the manifest file of the exe, we see that the <dependency> elements are all missing.

If we compile the same solution with an older VS (15.5.3), all the <dependency> elements are there again.

So is this a bug?

I've created 2 sample solutions, one compiled with VS 15.5.3 (WindowsFormsApp_Sample_Ok) and one compiled with VS 15.8.7 (WindowsFormsApp_Sample_Error)

ManifestIssue.zip

The first manifest file WindowsFormsApp_Sample_Ok\WindowsFormsApp_Sample\bin\Release\WindowsFormsApp_Sample.exe.manifest
containes the <dependency> element:

<dependency>
<dependentAssembly asmv2:dependencyType="install" asmv2:codebase="Native.ClassLibrary1.manifest" asmv2:size="1451">
<assemblyIdentity name="Native.ClassLibrary1" version="1.0.0.0" processorArchitecture="x86" type="win32" />
<hash xmlns="urn:schemas-microsoft-com:asm.v2">
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsigigestMethod Algorithm="XML-Signature Syntax and Processing" />
<dsigigestValue>2qRWxGXtoOZdiOeXFx1zh7QF/0vQtWXMDgWgQ3CKp40=</dsigigestValue>
</hash>
</dependentAssembly>
</dependency>

The second manifest file WindowsFormsApp_Sample_Error\WindowsFormsApp_Sample\bin\Release\WindowsFormsApp_Sample.exe.manifest
does NOT contain the <dependency> element.

Who can help?

Thanks a lot in advance,
Ulrich

Continue reading...