-
Notifications
You must be signed in to change notification settings - Fork 81
Upgrade Microsoft.WindowsAzure.Storage in SemanticLogging.WindowsAzure project #81
Comments
Seconded. This is what you get when you try using the new storage SDK:
As a workaround, you could implement a simple sink that pipes events to the System Diagnostics Trace and then have Azure upload them to Table Storage. See the following related SO discussion for a sample implementation: http://stackoverflow.com/questions/38141018/how-can-i-track-the-source-of-exception-on-trying-to-set-azure-sink-for-a-listen. Another (better, since you'd keep the schema) workaround would be to upload to Application Insights and use Continuous Export (not available in the free tier). Fortunately there's already a sink for that: https://github.com/fidmor89/SLAB_AppInsights. |
We're in the process of scheduling this work. My apologies for the lengthy delay. |
I ran into this today when trying to upgrade to all of the latest Azure tools and had to do my own patch to fix the problem. The fix is trivial. Just replace line 69 in WindowsAzureTableSink with the following:
This will compile. However, I have not yet been able to test because upgrading azure tools also blows up lots of other things. I'll post later when I see this working successfully. |
@robertmacgrogan thanks! |
I wanted to report that I finally was able to test and my fix as reported above works just fine. Not relevant here, but interesting to note that latest version of Microsoft.AspNet.SignalR.ServiceBus had the exact same issue. Thanks. |
Fixes #81: update Azure Storage dependency to 7.x
@paulirwin @mekoda Any idea when you will release an updated NuGet package? |
For me I downgraded and that solved my issue |
SemanticLogging.WindowsAzure references a very old version of Microsoft.WindowsAzure.Storage. Breaking changes in Microsoft.WindowsAzure.Storage v7.0 prevent redirecting.
The text was updated successfully, but these errors were encountered: