Multiple Dependency Versions Break Sandcastle Build Process

Topics: Developer Forum, Project Management Forum, User Forum
Aug 7, 2013 at 8:05 PM
How do you solve issues whereby multiple versions of the same NuGet package is used throughout the solution? For example, ProjectA depends on both NuGetA (v2) and ProjectB. Project B also depends on NugetA (but old version, v1).

When Sandcastle generates the documentation, it complains that it needs both v1 and v2 of NuGetA (which is not possible - only 1 NuGetA.dll can exist).

There is an old solution out there. I'm not sure if this still works with the current version of SHFB.

I was wondering if there have been new features to resolve this? Or a fix is on the way?
Aug 7, 2013 at 8:13 PM
Assuming it's MRefBuilder that's complaining about the missing reference, you can use the Assembly Binding Redirection plug-in to point the missing assembly reference at a different version.

Aug 7, 2013 at 8:34 PM
Thank you! That works perfectly. I used the "Ignore If Unresolved" option to avoid maintaining version bindings in the future.