Skip to content

Latest commit

 

History

History
40 lines (27 loc) · 1.97 KB

README.md

File metadata and controls

40 lines (27 loc) · 1.97 KB

BlazorRegisterNames

The package Windows.Azure.Bus is deprecated, u should use the Azure.Bus instead, probably will have a simillar workflow


We have 3 projects:

  • BlazorRegisterNames (In Blazor Server Side)
  • BusShared (the common part between the publisher and consumer)
  • ConsumeNames (The consumer in console .NET)

Steps:

Create a new azure bus resource

Select a subscription, resource group, configure a valid name, and a tier of pricing

To understand more about each tier and what he can give for us: https://azure.microsoft.com/pt-br/pricing/details/service-bus/

Create a new queue to receive messages

Configure infra inside of this queue

Select the size (how much messages this queue can gold)

Time to keep a message alive before dying

Lock duration to a message be consumed by only a consumer

Configure a key with acess policies (for example one with send and listen) or can be two different keys (one for listen and one for send)

Copy the addess of endpoint and key

Use the endpoint address in appsettings.json in the BLAZOR UI, and paste too in the program.cs the endpoint