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.

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

Storage Explorer assumes port 1000[0,1,2] for Storage Emulator #193

Closed
oxxa opened this issue May 17, 2018 · 1 comment
Closed

Storage Explorer assumes port 1000[0,1,2] for Storage Emulator #193

oxxa opened this issue May 17, 2018 · 1 comment
Assignees
Labels
💡 feature request New feature or request ⚙️ attach Related to attaching via keys, SAS, etc. ✅ merged A fix for this issue has been merged
Milestone

Comments

@oxxa
Copy link

oxxa commented May 17, 2018

Storage Explorer Version: 1.1.0

Platform: Windows

Architecture: ia32

Build Number: 20180507.1

Commit: bcc8990d

Regression From: Not a regression afaik

Steps to Reproduce:

This bug/missing feature relates to how Storage Explorer interacts with the Storage Emulator.

By default Azure Storage Emulator is setup to listen on ports http://127.0.0.1:10000 10001 and 10002 . On my system I have found another process grabs port 100000, so I have to start the Storage Emulator with it listening on another port range instead - via a change to its config file. That works fine and I can configure my VS project to talk to it, the issue is there seems to be no way to tell Storage Explorer that the emulator is now using different ports, instead it always tries to look for 10000, 10001 and 10002. Can an option be added so I can let it know about the ports the emulator is actually using? Or could Storage Explorer try to query the AzureStorageEmulator.exe.config file in C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator directory to see what ports it uses if it has trouble connecting?

image

Expected Experience:

I would like an option so that I can tell Storage Explorer what my Storage Emulator ports are.

Actual Experience:

I can't seem to find such an option to change the connection details for my local storage account.

@craxal
Copy link
Contributor

craxal commented May 17, 2018

Currently, you can't customize the endpoints for the emulator connection. That will be fixed in an upcoming release.

@craxal craxal added this to the 1.3.0 milestone May 17, 2018
@craxal craxal self-assigned this May 17, 2018
@craxal craxal added 💡 feature request New feature or request ⚙️ attach Related to attaching via keys, SAS, etc. labels May 17, 2018
@craxal craxal changed the title Storage Explorer assumes port 10000[0,1,2] for Storage Emulator Storage Explorer assumes port 1000[0,1,2] for Storage Emulator May 23, 2018
@craxal craxal added the pending label May 23, 2018
@craxal craxal modified the milestones: 1.3.0, 1.4.0 Jun 13, 2018
@craxal craxal added ✅ merged A fix for this issue has been merged and removed pending labels Jul 9, 2018
@craxal craxal closed this as completed Jul 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 feature request New feature or request ⚙️ attach Related to attaching via keys, SAS, etc. ✅ merged A fix for this issue has been merged
Projects
None yet
Development

No branches or pull requests

2 participants