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
Related
I am developing an application using Lucee.
Currently I have some files stored on an Azure Storage Account
and I need to be able to read and write to the Azure Storage account.
Is there any java api or Lucee Extension that can be used for this purpose?
There is indeed Azure Storage SDK for Java. The full documentation can be found here
It has support for blobs, Queues, Android and other libraries.
I liked #Adam-Smith-msft answer but I ended up using the code from https://github.com/paulklinkenberg/lucee-azure-provider so i did not have to deal directly with the Java SDK
I'm trying to use client side encryption for azure to securely upload files to blob storage in .NET,
However it seems that BlobEncryptionPolicy is not available and I have not seen any documentation specifying alternative solutions from microsoft.
Even their documentation still uses BlobEncryptionPolicy:
Client-Side Encryption and Azure Key Vault for Microsoft Azure Storage
Specifically i'm inside of a xamarin project using the latest .net version.
If i create a sample console app, I can reference BlobEncryptionPolicy without any issues. However the same nuget package inside a xamarin shared project can not resolve the reference to BlobEncryptionPolicy under the Microsoft.WindowsAzure.Storage.Blob namespace.
Does anyone know what is going on here?
There are some differences between Microsoft.WindowsAzure.Storage package depending on .net core and the one depending on .net framework.
You may have developed your Xamarin project based on .net core, where BlobEncryptionPolicy is not supported(this method doesn't exist in the dll).
As when you create a console app(.net framework), you can use the encryption. If you build a console app(.net core), you will find no such method as well.
An open issue on github about this, saying the encryption for .net core is coming soon.
You can change your targetframework to use it if .net core is not necessary for your development.
I currently need to store files into azure blob storage. I come across two different resources but not sure the second set of packages are for.
I probably only need the top two packages for accessing the Blob Storage.
using Microsoft.WindowsAzure.Storage;
using Microsoft.WindowsAzure.Storage.Blob;
From the https://learn.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-xamarin-forms-blob-storage, it say Connect to Azure Storage in your Xamarin.Forms app.
using Microsoft.WindowsAzure.MobileServices.Files;
using Microsoft.WindowsAzure.MobileServices.Files.Metadata;
using Microsoft.WindowsAzure.MobileServices.Files.Sync;
using Microsoft.WindowsAzure.MobileServices.Sync;
Problem with the first set of package required me to use Shared Library not PCL.
WindowsAzure.Storage (the first set of namespaces) is the client library for Azure Storage services. Microsoft.Azure.Mobile.Client.Files (the second set of namespaces) is a client extension for Azure Mobile Apps.
If you are using the Mobile Apps SDK and want to work within its abstractions then it makes sense to use the second library. If you want to have access to all of the features of Azure Storage then it makes sense to use the first project.
As of version 8.0, the Azure Storage client contains a netstandard 1.0 façade, which works like a PCL.
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.
The Windows Azure Storage package comes with a truckload of dependencies, including improbable libraries such as System.Spatial. I only intend to use the Blob Storage, which should represent about 5% of this package. Is there any stand-alone library available to do this?
You could always make direct REST API calls, as the storage API is well-documented. This is about as lightweight as you're going to get. There is no other official .net Azure SDK other than the one you referenced. I don't know of any 3rd-party .net SDKs available.