Reactive extensions nuget package name & public key change

[Tom Allard]

Reactive extensions have announced:

 

The NuGet packages have changed their package naming in the move from v2.x.x to v3.0.0

• Rx-Main is now System.Reactive
• Rx-Core is now System.Reactive.Core
• Rx-Interfaces is now System.Reactive.Interfaces
• Rx-Linq is now System.Reactive.Linq
• Rx-PlatformServices is now System.Reactive.PlatformServices
• Rx-Testing is now Microsoft.Reactive.Testing

This brings the NuGet package naming in line with NuGet guidelines and also the dominant namespace in each package. The strong name key has also changed, which is considered a breaking change. However, there are no expected API changes, therefore, once you make the NuGet change, no code changes should be necessary.

Also the old packages have been unlisted.

This breaks (The located assembly's manifest definition does not match the assembly reference.) using ravendb.client with subscriptions and updating system.reactive to 3.0.

Workaround:  Install-Package Rx-Main -Version 2.3.0-beta2 -Pre

[Fitzchak Yitzchaki]

RavenDB.Client doesn't have a dependency on Rx.

Can you list the steps to reproduce the issue or create a failing test?

Best Regards,

Hibernating Rhinos Ltd  

Fitzchak Yitzchaki l Senior Software Engineer l Mobile:+972-58-345-9538

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Allard]

Attached a failing test, after installing System.Reactive through nuget.

Fails with:

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

  ----> System.IO.FileLoadException : The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

   at Raven.Client.Document.Subscription`1.StartWatchingDocs()

   at Raven.Client.Document.Subscription`1..ctor(Int64 id, String database, SubscriptionConnectionOptions options, IAsyncDatabaseCommands commands, IDatabaseChanges changes, DocumentConvention conventions, Boolean open, Func`1 ensureOpenSubscription) in c:\Builds\RavenDB-Stable-3.0\Raven.Client.Lightweight\Document\Subscription.cs:line 86

   at Raven.Client.Document.AsyncDocumentSubscriptions.<OpenAsync>d__8`1.MoveNext() in c:\Builds\RavenDB-Stable-3.0\Raven.Client.Lightweight\Document\AsyncDocumentSubscriptions.cs:line 101

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Abstractions.Util.AsyncHelpers.<>c__DisplayClassb`1.<<RunSync>b__8>d__d.MoveNext() in c:\Builds\RavenDB-Stable-3.0\Raven.Abstractions\Util\AsyncHelpers.cs:line 75

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at Raven.Abstractions.Util.AsyncHelpers.RunSync[T](Func`1 task) in c:\Builds\RavenDB-Stable-3.0\Raven.Abstractions\Util\AsyncHelpers.cs:line 90

   at Raven.Client.Document.DocumentSubscriptions.Open(Int64 id, SubscriptionConnectionOptions options, String database) in c:\Builds\RavenDB-Stable-3.0\Raven.Client.Lightweight\Document\DocumentSubscriptions.cs:line 35

   at System.Reactive.RavenTestSample.TestCanReferenceReactiveExtensions() in C:\Temp\rxrdb\System.Reactive\System.Reactive\RavenTestSample.cs:line 28

--FileLoadException

[Oren Eini (Ayende Rahien)]

Can you try with the 3.5 client?

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

[Tom Allard]

It works with the 3.5 client (35165). 

(Although i had to set target platform to x64, otherwise i got a badimageformatexception. Probably not related)

Thanks,

Tom