Thanks for bringing this to my attention. There was an issue with the build and the wrong key was set to work with Enyim (which fooled the build verification). I’ve updated the NuGet package, which is listed at https://www.nuget.org/packages/CouchbaseNetClient/1.2.3.
It seems that Enyim.Caching.dll has a sign problem o this release. I get the following exception:
"Could not load file or assembly ‘Enyim.Caching’ or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)"
1.2.1 works as expected.
That’s the target. The challenge has been finding a way to reliably reproduce that error in an easily testable manner.
Thanks very much, this is working as expected.
As I see there is no fix for bad magic values, this bug has been shifted again to next release. Are we going to see a fix on the next release?