Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

Somewhere between versions 2.0.1 and 2.0.3 NuGet references to Microsoft.Azure.Storage.* libraries were updated to 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=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
uses 'Microsoft.Azure.Storage.Blob, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
which has a higher version than referenced assembly 'Microsoft.Azure.Storage.Blob'
with identity 'Microsoft.Azure.Storage.Blob, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

amnguyecommented, May 5, 2021

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.

mgroetancommented, Apr 30, 2021

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Nuget Version Mismatch Error occurs in two Solutions
Idea 1 Within both projects, open the packages.config file. See whether both files reference the same version of Microsoft.WindowsAzure.
Read more >
How to Fix the 'Could not load type 'Microsoft. ...
This error typically occurs when there is a mismatch between the version of the Microsoft Azure Storage library and the version expected by ......
Read more >
MSB3277: Found conflicts between different versions of ' ...
This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the...
Read more >
Azure Storage Explorer troubleshooting guide
Microsoft Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux....
Read more >
Common NuGet configurations
NuGet.Config files control NuGet's behavior, and can be modified with nuget ... Config file locations and uses; Changing config settings ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found