You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think the highlighted point is correct. After running Aspire, I don't have a queue named "queues" in my emulator. I think this sets the name to be used by the client to grab a connection string to the queue service.
The raised issue is correct - AddBlobs, AddQueues and AddTables API do not add/reference/provide access to individual Azure resources (like blob containers, queues or tables). Instead, those API reference respective Azure service clients that provide access to the individual resources.
In essence, those API return pointers to the Azure resource nodes and not items within those:
Type of issue
Other (describe below)
Description
I don't think the highlighted point is correct. After running Aspire, I don't have a queue named "queues" in my emulator. I think this sets the name to be used by the client to grab a connection string to the queue service.
Page URL
https://learn.microsoft.com/en-us/dotnet/aspire/storage/azure-storage-queues-integration?tabs=dotnet-cli#add-azure-queue-storage-resource
Content source URL
https://github.com/dotnet/docs-aspire/blob/main/docs/storage/azure-storage-queues-integration.md
Document Version Independent Id
ca5166fd-9731-3528-851f-0ae8cffdeeb7
Article author
@IEvangelist
Related Issues
Note
This content was automatically updated to filter out profanity. If you feel as though this was done in error, please file an issue with the details.
The text was updated successfully, but these errors were encountered: