Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Storage Explorer vs. MAX_path issue (260 character) when double clicking files #902

Closed
yuhaii opened this issue Nov 27, 2018 · 11 comments
Closed

Storage Explorer vs. MAX_path issue (260 character) when double clicking files #902

yuhaii opened this issue Nov 27, 2018 · 11 comments
Labels
💻 windows Related to Windows platforms ⚙️ blobs Related to blob storage ✅ duplicate Issue or pull request already exists

Comments

@yuhaii
Copy link

yuhaii commented Nov 27, 2018

Issue description:

Azure Storage Explorer creates two weird GUID folders within each other under temp before downloading the file including the folder structure containing the file.
This appears to be an issue often for users. Why have to folders with long GUIDs that only leave limited space for the folder structure and filename?
Users double click files in Azure Storage Explorer and expect the files to open in either Adobe Acrobat or Word, but nothing happens as the path exceed the allows 260 chars within Windows

Information:

Storage Explorer Version: 1.5.0
Platform/OS Version: Windows 10 Enterprise v1809
Architecture: ia32
Regression From: not sure

Steps to Reproduce:

    1. Create a pdf file with long name. Like "Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04Soft Skills-2017-12-04.pdf".

    2. Upload this file onto blob storage with "Azure Storage Explorer" tool:
      image

    3. Double click this long name PDF file on "Azure Storage Explorer" .
      image

      This pdf file will be opened by Edge browser and get error:

image

  1. Click "open folder" button on "Azure Storage Explorer", we can see the folder have a very long path : "C:\Users\yuhai\AppData\Local\Temp\31c46eb1d42b9769d500ee58062c7ecbbf63890e62277f7f62e7863d65a49a04".

  2. If we double click the long name pdf under folder : "C:\Users\yuhai\AppData\Local\Temp\31c46eb1d42b9769d500ee58062c7ecbbf63890e62277f7f62e7863d65a49a04". It also can't be correctly opened by Edge

6) If we copy the long name PDF file to "C:\Users\yuhai\Desktop" folder. This long name PDF file can be open correctly under this shot path folder.

Expected Experience:

Long name PDF file can be opened by Edge correctly

Actual Experience:

Long name PDF file can't be opened by Edge
@PeterSelchDahl
Copy link

Thanks for adding the issue. I also created a uservoice on Azure Feedback for this issue: https://feedback.azure.com/forums/217298-storage/suggestions/36102955-storage-explorer-vs-max-path-issue-260-character

@yuhaii
Copy link
Author

yuhaii commented Nov 30, 2018

Hello Team, do you have any update on this issue? Thank you!

@craxal craxal added ⚙️ blobs Related to blob storage 💻 windows Related to Windows platforms labels Dec 4, 2018
@craxal
Copy link
Contributor

craxal commented Dec 4, 2018

Apologies for the late reply. We've been swamped lately.

The GUID folders are designed to avoid file conflicts during downloads. Though I believe the long path name is a known issue. We can look into fixing this. In the meantime, is it possible to rename your blob something shorter to get around this issue?

@yuhaii
Copy link
Author

yuhaii commented Dec 5, 2018 via email

@craxal
Copy link
Contributor

craxal commented Dec 6, 2018

Duplicate of #93.

@craxal craxal closed this as completed Dec 6, 2018
@craxal craxal added the ✅ duplicate Issue or pull request already exists label Dec 6, 2018
@yuhaii
Copy link
Author

yuhaii commented Dec 10, 2018 via email

@yuhaii
Copy link
Author

yuhaii commented Dec 18, 2018 via email

@jinglouMSFT
Copy link

Expecting a fix release in a day or two.

@yuhaii
Copy link
Author

yuhaii commented Dec 19, 2018 via email

@jinglouMSFT
Copy link

The release is available now. Go to the release tab here in Github and download the bits for v1.6.1 build 20181218.1. The same bits will be available from the normal download page (storageexplorer.com) as well. It's in the process of being propagated as we speak.

@yuhaii
Copy link
Author

yuhaii commented Dec 19, 2018 via email •
edited by craxal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 windows Related to Windows platforms ⚙️ blobs Related to blob storage ✅ duplicate Issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@craxal @PeterSelchDahl @jinglouMSFT @yuhaii