Current v4.x framework referencing older Azure Storage libraries, causing conflicts with more updated libraries.
See original GitHub issueGithub issues should be used for bugs and feature requests. Use Stack Overflow for general “how-to” questions.
Version
Using bot builder 4.3.2,
Describe the bug
After updating Azure storage libraries to the most recent packages (Microsoft.Azure.Storage.Common, Microsoft.Azure.Storage.Blob, Microsoft.Azure.Cosmos.Table)
I get a compiler error on AzureBlobTranscriptStore .
Reference to type 'CloudStorageAccount' claims it is defined in 'Microsoft.Azure.Storage.Common', but it could not be found
It turns out Microsoft.Bot.Builder.Azure still references the older storage libraries.
Will this be updated to use the latest libraries?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Azure function app upgrade, function V4 ...
This blog will talk about some common issues you may meet when you try to upgrade your Azure function from older runtime version...
Read more >Troubleshoot Python errors in Azure Functions
The rest of this article helps you troubleshoot potential causes of this error by inspecting your function app's content, identifying the root ...
Read more >Troubleshoot dependency version conflicts - Azure
An overview of how to troubleshoot dependency version conflicts related to using the Azure SDK for Java.
Read more >Migrate apps from Azure Functions version 3.x to 4.x
This article shows you how to upgrade your existing function apps running on version 3.x of the Azure Functions runtime to be able...
Read more >what is the replacement for Microsoft.Azure.Storage.Blob ...
Therefore you cannot update that library to the new package because the namespaces are different. Therefore you'll have to continue referencing ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should not be closed. The gap between the versions of Storage is now getting far too large.
Turns out we can’t take these changes without breaking both code and binary compatibility.
We’ll have to stuck with what we’ve got for now.