strongnamer icon indicating copy to clipboard operation
strongnamer copied to clipboard

Build fails when a dependency uses a type from a second order dependency as a constant

Open Nick-Lucas opened this issue 8 years ago • 3 comments
trafficstars

This bug was discovered in the research under #10 and is caused by Mono.Cecil trying to resolve the .dll for a second order dependency, when the value of a compile time constant needs to be validated as part of writing an assembly.

When this happens the second order dependency cannot be resolved, since it's not in the project/bin/GAC folders, and the build fails.

Proposed solution is to implement a custom AssemblyResolver class and pass the list of solution assemblies in, for later resolution and returning.

Nick-Lucas avatar Feb 15 '17 18:02 Nick-Lucas

Hey @dsplaisted is StrongNamer still being maintained?

Nick-Lucas avatar Mar 01 '17 18:03 Nick-Lucas

Yes, sporadically. It hasn't need too much maintenance.

dsplaisted avatar Mar 01 '17 18:03 dsplaisted

Gotcha! Well I've got a bugfix for this issue under #12 which would be great to merge in with any changes you think are appropriate :)

Nick-Lucas avatar Mar 01 '17 18:03 Nick-Lucas