I have been using QueueClient to handle all functionality with the Storage Queue. I noticed in a few examples online that there is a CloudQueue, that has several more methods.
What is the difference between the two? Why would you use one over the other?
EDIT: I am using both Microsoft.Azure.Storage.Queue and Azure.Storage.Queues
Azure Storage client libraries for .NET - Azure for .NET Developers | Microsoft Docs
Azure.Storage.Queues are the v12 version of the SDK, Microsoft.Azure.Storage.Queue is the v11 version. . .
Typically we recommend using the latest version of the SDK, and typically only one version of the SDK per application.
Related
there are some code using v12 and some with v2.1.
and its very confusing sometimes.
this is with v2.1
block_blob_service = BlockBlobService(account_name=ACCOUNT_NAME, account_key=ACCOUNT_KEY)
and this one is with v12
blob_service_client = BlobServiceClient.from_connection_string(self.connection_string)
You should not be using version 2.1 as it is the legacy version of the SDK. You should always be using the latest version of the SDK (12.x at the time of writing this answer) as it will have support for all the new features Azure Blob Storage has to offer.
Though not recommended but the only reason one would want to use version 2.1 of the SDK if there's a need to have single SDK for managing all Azure Storage resources - Blobs, Files, Queues and Tables. With version 12, each resource type has a dedicated SDK.
I would like to use RedisTimeSeries module (latest feature) in Redis from .net core client in Azure.
I created Azure Cache for Redis (from RedisLabs) (https://azure.microsoft.com/en-us/services/cache/) standard resource in the Azure portal.
Downloaded the .net redis samples code from https://github.com/rustd/RedisSamples.
When I compiled samples code, it downloaded the nuget package called StackExchange.Redis (among other libraries).
Played with samples to understand how redis works from .net client.
It appears that raw REDIS commands where wrapped by StackExchange.Redis library.
Next, I wanted to play with RedisTimeSeries (as described at https://github.com/RedisTimeSeries/RedisTimeSeries).
The StackExchange.Redis .net library does not seem to provide any API to invoke RedisTimeSeries module related commands such as TS.CREATE, TS.ADD etc.
Here are my questions:
Is RedisTimeSeries module supported in Azure Cache for Redis (from RedisLabs)?
If supported, how do I invoke TS related commands from my .net core client?
If not supported, is there any other .net library that lets me do this?
Is RedisTimeSeries module supported in Azure Cache for Redis (from RedisLabs)?
Azure Cache for Redis, is not from RedisLabs but from MS, the only Redis vendor who currently supports Modules deployments is RedisLabs Cloud Pro (see: https://redislabs.com/redis-enterprise/deployments/ and https://redislabs.com/partner/microsoft/)
If supported, how do I invoke TS related commands from my .net core client?
DbSync.Execute("MyCommand", args)
It is coming soon on Azure Redis, see redis enterprise features on azure cache for redis coming soon
Enterprise tier will support RedisTimeSeries
RedisTimeSeries has been GA in Azure Cache for Redis, Enterprise Tier, since March 2021.
NRedisTimeSeries the recommended .Net client for RedisTimeSeries
As a Microsoft Azure services client, I received earlier today the following mail: http://aka.ms/Qga48e.
I was wondering how I could migrate my Blob storage without services disruption to use the latest Azure File Storage service.
Anybody has already performed this action? Any feedbacks will be welcomed.
Thanks.
I don't think that it would be necessary. Besides Azure Blob Service and Azure File Service serve different purposes all together and the things you could do with blob service can't be done through file service.
As mentioned in the newsletter, what you should try to do is upgrade your client applications to make use of latest version of storage client library. If you're using an older version of library (< 2.0), there would be some pain in migration but migrating from 2.0 to 4.x (currently latest version) should be rather painless.
Next thing you should look into is the default service version of your storage account services. If you're using .Net storage client library, you can fetch it via GetServicePropertiesAsync method. You can update the default service version using SetServicePropertiesAsync method.
You may also find this link helpful about understanding storage service versioning: http://msdn.microsoft.com/en-us/library/azure/dd894041.aspx.
UPDATE: 13-DEC-2014
Azure Storage Team has published a blog post which talks more about this issue: http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx.
The Storage Service REST API is not being removed. There are several versions of the API, from over the years. Older versions of the REST API (prior to the 2012-02-12 version) are being retired. But it's definitely not going away, and neither is the Azure Storage service.
Different versions of the SDKs (across the various language stacks) and command-line tools (PowerShell, CLI) may be using one of the older versions. If you're using the current versions of SDKs and command-line tools, this has no effect on you.
Consider how many versions there have been (all tracked here, and all listed in the page you linked to in your answer:
2014-02-14 (current)
2013-08-15
2012-02-12
2011-08-18
2009-09-19
2009-07-17
2009-04-14
If you're using an older version of an SDK or command-line tool, there's a chance that, in Dec. 2015, it won't work as expected anymore, as the underlying version will have been retired. So, essentially you have until December 2015 to update your Azure projects if needed.
I wanted to follow the guidance of “Windows Azure Storage and CORS” but I notice that my version of the Windows Azure SDK (2.1) does not have the members (like ServiceProperties .Cors) used in the article. I also notice that the documented members of ServiceProperties do not include Cors. Was this stuffed removed from the codebase or is this stuff so new that it is not documented yet? Is this CORS stuff in a future version of the SDK? Or do I have to use the REST API?
Storage Client Library (version 2.x) which comes with SDK 2.1 does not have support for CORS. It is supported in Storage Client Library version 3.x. So if you want to manage CORS settings, you would need to use that library. You can download this library through Nuget: http://www.nuget.org/packages/WindowsAzure.Storage. You could always use REST API if you want to.
However, please keep in mind that SDK 2.1 is not compatible with version 3.x of storage client library. What that means is that if you use 3.x version of storage client library in your project you won't be able to use storage emulator. You would always need to connect to cloud storage account for development.
Windows Azure Blobs, Tables and Queues now support CORS to enable users to access/manipulate resources from within the browser serving a web page in a different domain than the resource being accessed.
http://msdn.microsoft.com/en-us/library/windowsazure/dn535601.aspx
Just like we have SDK for the Azure Storage [Tables, Blobs, Queues] along with the REST API;
Do we have SDK or library for handling Service Management APIs in c#...?
Naveen,
Take a look at "Microsoft.WindowsAzure.ServiceManagementClient.dll". You can find this along with Azure SDK (C:\Program Files\Windows Azure SDK\v1.4\bin directory). I think this is what you're looking at.
Hope this helps.
There's not an SDK as such, but there is this sample from Microsoft which demonstrates how you can work with the REST API in .net. The other option is you could just use the sample code as it is.
UPDATE:
MS now have a pre-release version of a management library available on NuGet. Brady Gaster has a blog to get you started.
knightpfhor's comment is correct, but since the comment we've released the MAML 1.0 libraries. I think the Storage Management Client package might be what you're after.