Azurite Support on Visual Studio

[justinyoo]

I'm using Visual Studio 2017. and not sure whether it's the same issue on Visual Studio 2019 or not.

When I run VS2017 to debug an Azure Functions app, although I have Azurite running, it throws the error like this:

It seems that VS2017 only looks for Azure Storage Emulator. However, this document says that

Azurite is the future storage emulator platform. Azurite supersedes the Azure Storage Emulator.

It's OK it's not supporting Azurite at the moment, but I wonder whether:

• There is an overriding feature to opt-out Storage Emulator and opt-in Azurite, and
• When Azurite support is planned.

Just for the record, if I run the Function app in a command prompt by running the func host start, it's all good. The error only happens on Visual Studio.

[hebronwatson]

I'm having the same issue on VS2019, so a response would be appreciated.

[kmr299]

I'm having the same issue on VS2019 😑

[kmr299]

I was able to solve the problem by starting AzureEmulator manually.
To solve the problem, you must go to the "C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator" path and run this command: "AzureStorageEmulator.exe start -inprocess" and run the project in visual studio again.

[RossHammerAtSterling]

I have just uninstalled my Azure Storage Emulator and installed Azurite per the messaging that the old storage emulator is out and this is now "the thing to use". Yesterday, before switching, my VS solution was running fine with the old Storage Emulator. Today, after the uninstall and new install, I just get a message from VS when I attempt to debug, "Could not locate the Azure Storage emulator executable." I cannot find any references to this anywhere else.

Microsoft Visual Studio Professional 2019
Version 16.7.2

λ azurite --version
3.9.0
λ azurite
Azurite Blob service is starting at http://127.0.0.1:10000
Azurite Blob service is successfully listening at http://127.0.0.1:10000
Azurite Queue service is starting at http://127.0.0.1:10001
Azurite Queue service is successfully listening at http://127.0.0.1:10001

Edit:
My configuration was using the recommended short-form connection value, "UseDevelopmentStorage=true".
When I switched it to the full HTTP connection string, it appears to be working so far.
https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azurite#http-connection-strings

[RossHammerAtSterling]

I was able to solve the problem by starting AzureEmulator manually.
To solve the problem, you must go to the "C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator" path and run this command: "AzureStorageEmulator.exe start -inprocess" and run the project in visual studio again.

That assumes still using the old Azure Storage Emulator, which is no longer under development. The point of the OP is to use the new Azurite emulator.

[mwwhited]

It's really sad that the free dev tool stack is getting preferential treatment over those of us that spend hundreds if not thousands of dollars on development tools. Support for Visual Studio is required if you are deprecating the storage emulator.

[acrigney]

yes we need support for c#

[HenrikSommer-Energinet]

It seem you can get around this problem.
By change Azure Storage Emulator to a new default port change-running-ip-of-azure-storage-emulator

And starte Azurite on default port.
Then VS2019 will start storage emulator on new port but your function will run on Azurite (default port)

[SeanFeldman]

cc @anthonychu

[varlen]

Doing it, I was only able to run my function in Visual Studio with Azurite after creating a $logs container manually through the REST API with curl -XPUT "http://localhost:10000/devstoreaccount1/%24logs?[SAS] where [SAS] is the SAS string. Refer this comment on how to create it.

[SeanFeldman]

@varlen you can work around it but it's not a solution. I'm using Rider and don't have to worry about creating $logs folder. That's not a solution though. Anyone using VS should be able to hit F5 and run.

[acrigney]

Any comments on performance of this? Parallel processing etc?

…

On Thu, 28 Jan. 2021, 1:51 am HenrikSommer-eng, ***@***.***> wrote: It seem you can get around this problem. By change Azure Storage Emulator to a new default port change-running-ip-of-azure-storage-emulator <https://stackoverflow.com/questions/37119066/change-running-ip-of-azure-storage-emulator> And starte Azurite on default port. Then VS2019 will start storage emulator on new port but your function will run on Azurite (default port) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1343 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCSC7KTTKEV2AR5DCTYPYDS4ASAFANCNFSM4I3QWAEA> .

[RDavis3000]

Its June 2021 and this is still not fixed

[anthonychu]

You can start Azurite on your own and prevent VS from trying to start the Storage Emulator by adding this to your csproj: <StartDevelopmentStorage>false</StartDevelopmentStorage>. There's work happening in the VS team to better integrate with Azurite.

[mwwhited]

You can start Azurite on your own and prevent VS from trying to start the Storage Emulator by adding this to your csproj: <StartDevelopmentStorage>false</StartDevelopmentStorage>. There's work happening in the VS team to better integrate with Azurite.

Good to know the thousands of dollars I've spent on Visual Studio Professional gets me better tooling... :/ constantly various dev teams from Microsoft talk about how a particular feature doesn't get much utilization so it gets tossed out or deprioritized (see inteillitest, code contracts, service bus emulator, architecture modeling, azurite, .Net 5 azure functions) and yet if you made the tools properly integrated in the skus the majority of paying users use you will see a massive uptick in usage.

We appreciate the effort but you guy was getting in a habit of only getting product and tools 80% useful and then you kill them off for the next shiny thing. It shouldn't be too much to ask for paying customers that want to love your products to get the integration and support they deserve.

[ghost]

It's October 2021, two years from the initial report, and this still happens despite the fact that an article from as recently as August 2nd of this year tells us to use this tool instead of Azure Storage Emulator.

[anthonychu]

Azurite is the default Storage emulator in VS 2022.

[louisoftokyo]

Azurite is the default Storage emulator in VS 2022.

Does this apply to Visual Studio for Mac 2022 too?

[acrigney]

But does Azurite have full functionality? Storage emulator was not designed to scale.

…

On Mon, Nov 1, 2021 at 8:27 PM Louis ***@***.***> wrote: Azurite is the default Storage emulator in VS 2022. Does this apply to Visual Studio for Mac too? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1343 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCSC7KRMXHFTUFQYTI5HO3UJZMQLANCNFSM4I3QWAEA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[itorian]

Faced the same issue, here are the steps to resolve it for Visual Studio 2019.

1. Make sure to uninstall 'Azure Storage Emulator'
2. Install azurite, you should see successfully started message, refer doc https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azurite?tabs=visual-studio#install-and-run-azurite
3. In local.settings.json AzureWebJobsStorage value should be DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;

This would solve the issue.

[RobBowman]

Azurite is the default Storage emulator in VS 2022.

I'm using VS 2022 Enterprise v17.0.4. Azurite works ok with new Azure Functions (C#) projects. Is it possible to convince projects that were originally created using VS2019 to now use Azurite rather than the legacy storage emulator?