Mismatch between actual versions of Microsoft.Azure.Storage.* libraries used and those reported by NuGet.

[older]

Somewhere between versions 2.0.1 and 2.0.3 NuGet references to Microsoft.Azure.Storage.* libraries were updated to 11.2.2.0 while .nuspec file still says that version 11.2.0 is used. When I update my project to 2.0.3 I get the following error:

error CS1705: Assembly 'Microsoft.Azure.Storage.DataMovement'
with identity 'Microsoft.Azure.Storage.DataMovement, Version=2.0.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
uses 'Microsoft.Azure.Storage.Blob, Version=11.2.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
which has a higher version than referenced assembly 'Microsoft.Azure.Storage.Blob'
with identity 'Microsoft.Azure.Storage.Blob, Version=11.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

[mgroetan]

I've noticed "the same", although the case is that it DID use to reference "11.2.2", whereas now it instead references the much older "11.2.0" version.
If you compare the 2.0.1 and 2.0.2 releases, you'll see that the ".nuspec" file said "11.2.0" all the time, whereas for sure, the Visual Studio package manager showed "11.2.2":

Selecting either 2.0.2 or 2.0.3 will show this:

If you look at the change log, it states that in version 2.0.0, the refs were updated from "11.1.2" to "11.2.2":

If you diff the 1.3.0 and 2.0.0 versions, you see that lots of project files and "packages.config" files got updated to ref the new "11.2.2" version. BUT the ".nuspec" file was actually updated to target only "11.2.0"!

So, apparently something fishy happened with regard to that ".nuspec" file, which led to the current mess-up.

[mgroetan]

In any case, I realize that we're dealing with a package that will eventually be deprecated, along with its "sister" packages in the "Microsoft.Azure" series, in favour of the new "Azure" series of packages. This has also been explicitly added to the readme file in the 2.0.2 version (you easily see that in the differ linked to above).
On that topic, I haven't yet been able to find an easy migration route, also seeing that the "Transfer data" section of the storage doc still points to this package.

I'm specifically looking for an alternative to the "TransferManager" class. I'd deeply appreciate if anyone in the team could point me in the right direction.

[amnguye]

We are looking upping the version of Microsoft.Azure.Storage.* libraries soon and making another release of the DataMovement library to resolve this problem soon.

[amnguye]

We will also look to upgrade to 11.2.3 due to a major fix made in the Microsoft.Azure.Storage.Blob, Files, and Common package where there was a race condition in UploadStream which the DataMovement library takes advantage of.

[amnguye]

Please kindly upgrade to 2.0.4 to avoid the mismatch error of the Microsoft.Azure.Storage.* libraries. Also we've upgraded to 11.2.3 of the Microsoft.Azure.Storage.Common, Blob, and File to avoid the race condition when uploading streams.