Skip to main content

Azure Tools - Azure Cloud Explorer

Highlights of  Azure Cloud Explorer
Azure Services: Azure Blob Storage
Cost: Free of use
How it is delivered: Installer
Top 3 features:
     #1 Looks and feel like File Explorer
     #2 Drag and drop functionality
     #3 Integrated with local file storage
Pain points:
     #1 Lack of support for virtual directories (e.g. OneDrive)
     #2 Linux support
     #3 Hard to find download link using search engine
Download URL:
     Monza Cloud

First time when I discovered these tools was a few months ago. I was looking for a method for copying data from Azure Blob Storage to the local disk for non-technical people. Imagine that you need to share content with somebody from HR knows to use only Office and Windows. For them, a tool that looks like Windows File Explorer is perfect.
The first thing that impressed me at the tools what the similarities with File Explorer. The initial look and feel are almost the same. As you can see below the icons, the position of the content and the features are the same. I like that that copy&paste and drag and drop are working seamlessly. With the current UI, even my mother that has 70+ years old can use Azure Storage without a problem for sharing content.

You can use the local emulator storage or you can add any Azure Storage account using a SAS key, connection string or using the <storage account name, key> tuple. For each path (aka folder) or blob inside the Azure Storage, you can see properties (e.g. size, ETag, last modified date) or manage the SAS or permissions if needed.
You can add multiple storage accounts for which you are allowed to copy content between them or to the local storage. Even if you don’t see the virtual folders like OneDrive ones, you can bookmark it and access from there later on.
Until now, I didn’t have any issues with the tool or limitations. I even create a script that installs automatically Azure Cloud Explorer and configure the Azure Storage accounts. In this way, a non-technical use has the tool ready for use in just a few seconds.

Azure Cloud Explorer is one of that kind of tools that people don’t know about it, even if the tool is free and provide the same experience as you have with File Explorer when you upload/download content from Azure Blob Storage. It’s the perfect tool for non-IT people. You should give it a try.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…