Skip to content

jwendl/azure-signalr-wpf-example

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Azure SignalR + Functions + WPF Example

An example of using Azure Signal R service to send data from one endpoint to several other endpoints.

Intent

The intent of this repository is to serve as an example of how to set this up in a serverless fashion. If you run into issues setting it up please post an issue on the repo. And if you want to add a PR - all contributions are welcomed.

Steps to Reproduce

  1. Clone the repository
  2. Go into the [repo-root-folder]/deploy/aad
  3. Run the following in a bash shell ./create-application.sh -p [prefix] -s [postfix] where [prefix] is the resource prefix and [postfix] is the resource postfix
  4. After it finishes, record the output as we will need some of the values later
  5. Next we will create an Azure AD Application registration using the steps below
    1. Go to the Azure Portal and click on Azure Active Directory
    2. Inside Azure Active Directory, go into App Registrations
    3. Find the application registration we just created, will be named something like [prefix]visualassist[postfix]
    4. Inside the application registration screen select Authentication on the left
    5. Inside the Authentication tab, click on the button "Add a platform"
    6. When the new blade shows up, select Mobile and desktop applications
    7. Inside there, add a custom redirect URI of http://localhost/
    8. Save that data and it should now show up
    9. On the left select "Expose and API"
    10. From that screen, select the "set" button and it should name your application api://[guid] where [guid] is some unique identifier
    11. From that point, click on the "Add a scope" button
    12. Inside that window, enter "publish" as the scope name
    13. Go ahead and fill the required fields with anything you want and then ensure the state is Enabled
    14. After that click on Add scope
  6. Navigate into the [repo-root-folder]/deploy/bicep folder
  7. Run the following shell script in bash ./deploy-azure.sh -p [prefix] -s [postfix] -g [resource-group-name] -l [location] -a [valid-audience] where the values are in the table below
  8. Navigate into the [repo-root-folder]/deploy/application folder
  9. Run the following shell script in bash ./deploy-application.sh -p [prefix] -s [postfix] where [prefix] is the resource prefix and [postfix] is the resource postfix
  10. Double check that all the resources are deployed to Azure, it should be a SignalR Service, Function Application and Application Insights instance
  11. Open up the [repo-root-folder]/src/ui/VisualAssist.UserInterface.sln solution file
  12. Once inside there, go into the App.config file
  13. Change the values to be what you need in your environment description in the table below

Variables

Bicep Variables

Variable Description Example
prefix The resource prefix jw
postfix The resource postfix dev
resource-group-name The resource group name for your Azure resources TestGroup
location The location, I used westus2 westus2
valid-audience The Azure AD application audience, example api://[azure-ad-app-id] api://89c7d6ac-586a-4dc8-bbc3-1c8952c2f757

UI Variables

Variable Description Example
ClientId The Azure AD Client ID (or App ID) 89c7d6ac-586a-4dc8-bbc3-1c8952c2f757
Tenant Your Azure AD Tenant (az account show) 72f988bf-86f1-41af-91ab-2d7cd011db47
Instance The instance your Azure AD application is in https://login.microsoftonline.com/
Scope The scope for your application api://89c7d6ac-586a-4dc8-bbc3-1c8952c2f757/publish
SignalRNegotiateEndpoint The URI to your function application https://jweafadev.azurewebsites.net/api
FunctionAppUrl The root URI for your function app https://jweafadev.azurewebsites.net/

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published