Redirect not added even though it's necessary when library is built with a newer (but not required) version of a dependency.

Solution S:

• Project A, L >= v1
• Project B, L == v2

S will correctly use L v2.

A is the interesting thing here. The project is built with v2, and this is
clearly indicated in the DLL so it is able to load the correct version. On the
other hand, it correctly works with v1 too, so the nuspec only states >= v1.

And here comes the problem. When adding a dependency for A, no redirect is added
for L even though we have redirects: on. This means A will try to load v2 even
if the solution requires v1 because of some other library.

As a workaround, it's possible to add nuget L redirects: force to the solution
requiring A.

I believe paket should add a redirect if the library is built with a higher
version than it requires.

The report describes Paket's redirects: on behavior for a dependency built against a newer assembly version. Start by reproducing the A/B/L scenario with redirects enabled and compare it with redirects: force; done means normal mode adds the needed redirect while preserving the >= dependency constraint.