Binding redirect at compile time for strong named assembly
<p>We have a question about assembly binding redirection at compile time:</p>

<ul>
<li>Team V (the Veterans) is developing Product P1</li>
<li>P1 is continuously developed by Team V in two branches (branch 1.6.x and 1.7.x), so the version from Product P1 is incrementing over time in both branches</li>
<li>Team NG (New Generation) has built a Product P2 based on Product P1 (using certain assemblies from P1 branch 1.7)</li>
<li>Product P2 contains an Assembly A2 (strongly named) that helps implementing any Product (P2, P3...) that is based on P1</li>
<li>Team NG created a Nuget Package for Assembly A2 (which is referring certain assemblies from P1 branch 1.7)</li>
<li>Now, Team NG has started Product P3 and has to use Assembly A2 from P2 and an Assembly A1 from P1</li>
<li>Assembly A1 from P1 is also available as Nuget Package, but in version 1.6 (because 1.7 is not approved yet for Product P3)</li>
<li>So Team NG has now Product P3 with two references: A2 and A1</li>
<li>The problem now is, that A2 refers A1 in version 1.7 but we only have A1 in version 1.6</li>
<li>Team NG is not allowed to use A1 in version 1.7</li>
</ul>

<p>This is why we are looking for a binding redirect at compile time for strongly named assemblies. As far as I know (by investigations), the 'Specific Version' property has no effect when setting this for a strongly named assembly.</p>

<p>Is such a redirection possible or are there any other suggestions?</p>

<p>Many thanks in advance
Regards, Michael</p>