Closed yannickrondeau closed 1 year ago
Sounds good to me, please raise a PR. I haven't used Azurite yet other than from azure functions emulator indirectly so can't confirm how it works - you have my full trust and support, should be a great addition.
@YannickRondeau are you doing a PR?
If not I can look at doing one, looking to provide more storage options for the thing I'm developing and this NuGet is perfect, but I use Azurite for local development.
@IeuanWalker I haven't work on anything yet. For our project, we've decided to go directly with the Azure Storage SDK which was easier in our case.
Hi 👋
The previous version Storage.Net is supporting the
emu
account while in development. It doesn't seem like stowage is supporting it. I looked at the source code and couldn't find any way of connecting, easily, to the emulator. Therefore, I revised the current implementation and do have one issue.To address the issue, I used the same approach as @iamkoch which is allowing to override the azure endpoint. It worked great; however, it looks like using the
http://127.0.0.1:10000/devstoreaccount1
endpoint with a container (emu in this example) lead to an issue with the emulator not looking at the right account. To address that, I had to set myContainerName
todevstoreaccount1/emu
.Here is the code I changed to get things working. If you prefer, I can create a pull request to start a discussion.
Files.cs
AzureBlobFileStorage.cs
I guess I could keep it that way, but I find it a bit confusing to put the storage account in the container name when in development. Haven't tested in production with Azure Storage yet.
Thanks,