Incompatibility between System.Reactive.Core and System.Reactive.Windows.Threading 3.1.1 NuGet packages

[hickford]

I might be wrong, but I believe there's an incompatibility between the System.Reactive.Core and System.Reactive.Windows.Threading 3.1.1 NuGet packages

1. https://www.nuget.org/packages/System.Reactive.Core/3.1.1
2. https://www.nuget.org/packages/System.Reactive.Windows.Threading/3.1.1

Projects in my solution reference both System.Reactive.Core and System.Reactive.Windows.Threading. I extracted the assemblies from the NuGet packages. When I build my solution, it gives a build warning:

warning MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190

With diagnostic logging on it gave a bit more information:

 There was a conflict between "System.Reactive.Core, Version=3.0.3000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263" and "System.Reactive.Core, Version=3.0.0.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263".
     "System.Reactive.Core, Version=3.0.3000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263" was chosen because it was primary and "System.Reactive.Core, Version=3.0.0.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263" was not.
     References which depend on "System.Reactive.Core, Version=3.0.3000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263" [C:\bin\System.Reactive.Core.dll].
         C:\bin\System.Reactive.Core.dll
           Project file item includes which caused reference "C:\bin\System.Reactive.Core.dll".
             System.Reactive.Linq
     References which depend on "System.Reactive.Core, Version=3.0.0.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263" [].
         C:\bin\System.Reactive.Windows.Threading.dll
           Project file item includes which caused reference "C:\bin\System.Reactive.Windows.Threading.dll".
             System.Reactive.Windows.Threading

At runtime it gives this error:

Could not load file or assembly 'System.Reactive.Core, Version=3.0.1000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

[hickford]

These are the files I extracted from the NuGet packages:

nuget System.Reactive.Core 3.1.1 [lib\net46\System.Reactive.Core.dll|lib\net46\System.Reactive.Core.xml]
nuget System.Reactive.Windows.Threading 3.1.1 [lib\net45\System.Reactive.Windows.Threading.dll|lib\net45\System.Reactive.Windows.Threading.xml]

Inspecting System.Reactive.Windows.Threading.dll in a disassembler, it references

// System.Reactive.Core, Version=3.0.1000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263
// System.Reactive.Interfaces, Version=3.0.1000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263

Yet the copy of System.Reactive.Core.dll is a different assembly version

// System.Reactive.Core, Version=3.0.3000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263

Compare 3.0.1000.0 vs 3.0.3000.0

[hickford]

Any ideas, what's going on?

[clairernovotny]

As per #205, this is expected. MSBuild should be generating binding redirects for you though. Do you have AutoGenerateBindingRedirects enabled?

[jairbubbles]

Hi, I've encountered a similar issue .

Here is a nimimal example where you can see the issue: Issue305.zip (just launch the project)

AutoGenerateBindingRedirects is true in the .csproj so I think binding redirect might not work with nested package dependencies.

The project is targeting .NET framework 4.6. With 4.5 you won't have the issue as version will be 3.0.1000 for all assemblies.
Why not all packages from Rx.net are targetting .NET framework 4.6 ?

[mediabuff]

Agreed. This is situation is absolutely ridiculous. Please fix the disparate packages nightmare !

[clairernovotny]

This has been fixed in the v4.0 alpha's on the MyGet feed

[mediabuff]

Thank you onovotny. Great!

Hello @onovotny ,
is it possible to release a 3.1.2 nuget (bugfix) package that will fix these issues? In our company we are not allowed to use alpha software (medical software) and these assembly redirects are not created automatically.
We think this a major issue after upgrading from Rx-Main to System.Reactive.