Skip to content

v1.1.0
Compare
Choose a tag to compare
@jinglouMSFT jinglouMSFT released this 26 Oct 21:26
v1.1.0
3889c35
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

05/09/2018

New

  • Storage Explorer now supports the use of Azurite. Note: the connection to Azurite is hardcoded to the default development endpoints.
  • Storage Explorer now supports Access Tiers for Blob Only and GPV2 Storage Accounts. Learn more about Access Tiers here.
  • A start time is no longer required when generating a SAS.

Fixes

  • Retrieving of subscriptions for US Government accounts was broken. This issue has been fixed. #61
  • The expiry time for access policies was not correctly being saved. This issue has been fixed. #50
  • When generating a SAS URL for an item in a container, the name of the item was not being appended to the URL. This issue has been fixed. #44
  • When creating a SAS, expiry times that are in the past would sometimes be the default value. This was due to Storage Explorer using the last used start and expiry time as default values. Now, every time you open the SAS dialog, a new set of default values is generated. #35
  • When copying between Storage Accounts, a 24-hour SAS is generated. If the copy lasted more than 24 hours, then the copy would fail. We've increased the SAS's to last 1 week to reduce the chance of a copy failing due to an expired SAS. #62
  • For some activities clicking on "Cancel" would not always work. This issue has been fixed. #125
  • For some activities the transfer speed was wrong. This issue has been fixed. #124
  • The spelling of "Previous" in the View menu was wrong. It is now properly spelled. #71
  • The final page of the Windows installer had a "Next" button. It has been changed to a "Finish" button. #70
  • Tab focus was not visible for buttons in dialogs when using the HC Black theme. It is now visible.#64
  • The casing of "Auto-Resolve" for actions in the activity log was wrong. It is now correct. #51
  • When deleting an entity from a table, the dialog asking you for confirmation displayed an error icon. The dialog now uses a warning icon. #148

Known Issues

  • If you use VS for Mac and have ever created a custom AAD configuration, you may be unable to sign-in. To work around the issue, delete the contents of ~/.IdentityService/AadConfigurations. If doing so does not unblock you, please comment on this issue.
  • Azurite has not yet fully implemented all Storage APIs. Because of this, there may be unexpected errors or behavior when using Azurite for development storage.
  • In rare cases, the tree focus may get stuck on Quick Access. To unstick the focus, you can Refresh All.
  • Uploading from your OneDrive folder does not work because of a bug in NodeJS. The bug has been fixed, but not yet integrated into Electron.
  • When targeting Azure Stack, uploading certain files as append blobs may fail.
  • After clicking "Cancel" on a task, it may take a while for that task to cancel. This is because we are using the cancel filter workaround described here.
  • If you choose the wrong PIN/Smartcard certificate, then you will need to restart in order to have Storage Explorer forget that decision.
  • Renaming blobs (individually or inside a renamed blob container) does not preserve snapshots. All other properties and metadata for blobs, files, and entities are preserved during a rename.
  • Although Azure Stack doesn't currently support Files Shares, a File Shares node still appears under an attached Azure Stack storage account.
  • The Electron shell used by Storage Explorer has trouble with some GPU (graphics processing unit) hardware acceleration. If Storage Explorer is displaying a blank (empty) main window, you can try launching Storage Explorer from the command line and disabling GPU acceleration by adding the --disable-gpu switch:

./StorageExplorer.exe --disable-gpu

  • For Linux users, you will need to install .NET Core 2.0.
  • For users on Ubuntu 14.04, you will need to ensure GCC is up-to-date - this can be done by running the following commands, and then restarting your machine:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

  • For users on Ubuntu 17.04, you will need to install GConf - this can be done by running the following commands, and then restarting your machine:

sudo apt-get install libgconf-2-4

Assets 5
Loading