ILMerge and component licensing problems

[drewnoakes]

Hi,

I'm using ILMerge to combine various assemblies. Everything works bar one
problem... the 3rd party licensed components no longer see the embedded
licensing information.

According to ILDAsm, both the original primary assembly and the merged
output assembly contain the appropriate .mresource entry in their manifests.

I'm wondering whether there's something fundamental about the license file
that means types that were previously in a different assembly no longer
believe they are suitably licensed after merging, and give annoying popups.

I've used LC.exe to create my own compiled license file, but the only way
I've found to add it into an assembly requires doing so at the compilation
stage.

Has anyone else come up against this, or does anyone understand the guts of
System.ComponentModel licensing well enough to shed some light?

Thanks,

Drew Noakes.