title: How to deploy and host .NET Core self-hosted console apps in Azure?
body: <p>App 1: I have a React app (based on create-react-app) which I've added as a Web App in Azure - that was pretty straight-forward to setup. This is using the JS SignalR client to communicate with the server, mentioned next.</p>
  
  <p>App 2: This app is the ASP.NET Core <a href="https://github.com/aspnet/SignalR" rel="noreferrer">SignalR</a> Server application created with dotnet new console. This app exposes a SignalR endpoint and is "self hosted".</p>
  
  <p>App 3: A 2nd ASP.NET Core console app is setup as a SignalR client. This is responsible to fetching some data, and sends those data to the SignalR server. This takes the SignalR endpoint (url) as a commandline argument.</p>
  
  <p>Running all this locally is pretty straightforward:</p>
  
  <p>App 1: npm start / serve -s build</p>
  
  <p>App 2: dotnet run -commandline args (runs on localhost taking a hubpath and port from the args supplied. The port is so that multiple instances SignalR servers can run on localhost - not sure if this is the way to do it in Azure or if they're differentiated with separate urls and hosted seperately there)</p>
  
  <p>App 3: dotnet run "<a href="http://localhost:5000/somenotificationhubname" rel="noreferrer">http://localhost:5000/somenotificationhubname</a>"</p>
  
  <p>I've added a bat file in each of the console apps, so I can open multiple instances of those, with different args.</p>
  
  <p>So locally it runs as easily as clicking 3 bat files.</p>
  
  <p>But I'm kinda lost on how to host all this in Azure. The web app seemed pretty straightforward. I just created a web app in Azure, connected to it through an FTP client and copied over the contents of the build folder from the React app.</p>
  
  <p>But what to do with the ASP.NET Core console applications so that the SignalR console app will be hosted in Azure and has its endpoint exposed for the other 2 apps to consume?</p>
  
  <p>I tried adding both both App 2 and 3 as webjobs under App 1, but that didn't seem to work.</p>
  
  <p>I've also heard that SignalR should not be running on IIS, so would it make sense to make it self-contained (exe) and run it inside a docker container? Any help is much appreciated.</p>