upgrade to .net 6.0 for some samples (#186)

* upgrade to .net 6.0 for some samples

* add DockerFile for some samples

* update README about docker deployment

* update Dockerfile and Readme for some samples

* update readme for some samples

* update dockerfile

samples/AdvancedChatRoom/AdvancedChatRoom.csproj

@@ -1,6 +1,6 @@
 <Project Sdk="Microsoft.NET.Sdk.Web">
   <PropertyGroup>
-    <TargetFramework>netcoreapp3.1</TargetFramework>
+    <TargetFramework>net6.0</TargetFramework>
     <UserSecretsId>advancedchatroom</UserSecretsId>
     <RootNamespace>Microsoft.Azure.SignalR.Samples.AdvancedChatRoom</RootNamespace>
     <PackageVersion Condition=" '$(SDKVersion)' != '' ">$(SDKVersion)</PackageVersion>

samples/AdvancedChatRoom/Dockerfile

@@ -0,0 +1,6 @@
+FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
+WORKDIR /src/AdvancedChatRoom
+
+COPY ./. ./
+RUN dotnet restore && dotnet build
+ENTRYPOINT ["bash", "-c", "dotnet run --urls http://0.0.0.0:80"]

samples/AdvancedChatRoom/Properties/launchSettings.json

@@ -21,7 +21,7 @@
       "environmentVariables": {
         "ASPNETCORE_ENVIRONMENT": "Development"
       },
-      "applicationUrl": "http://localhost:5000/"
+      "applicationUrl": "http://0.0.0.0:5000/"
     }
   }
 }

samples/AdvancedChatRoom/README.md

@@ -22,4 +22,12 @@ dotnet user-secrets set Azure:SignalR:ConnectionString "<your connection string>
 dotnet run
 ```
 
+## Quick Deploy via Docker image
+You can also deploy this sample via existing docker image
+
+```
+docker run -e Azure__SignalR__ConnectionString="<signalr-connection-string>" \
+           -p 5000:80 mcr.microsoft.com/signalrsamples/advancedchatroom:latest
+```
+
 Open the broswer with url `localhost:5000`, you can see the sample just like Chat Sample but has more operations. 

samples/ChatRoom/ChatRoom.csproj

@@ -1,6 +1,6 @@
 <Project Sdk="Microsoft.NET.Sdk.Web">
   <PropertyGroup>
-    <TargetFramework>netcoreapp3.1</TargetFramework>
+    <TargetFramework>net6.0</TargetFramework>
     <UserSecretsId>chatroom</UserSecretsId>
     <RootNamespace>Microsoft.Azure.SignalR.Samples.ChatRoom</RootNamespace>
   </PropertyGroup>

samples/ChatRoom/Dockerfile

@@ -0,0 +1,6 @@
+FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
+WORKDIR /src/ChatRoom
+
+COPY ./. ./
+RUN dotnet restore && dotnet build
+ENTRYPOINT ["bash", "-c", "dotnet run --urls http://0.0.0.0:80"]

samples/ChatRoom/Properties/launchSettings.json

@@ -21,7 +21,7 @@
       "environmentVariables": {
         "ASPNETCORE_ENVIRONMENT": "Development"
       },
-      "applicationUrl": "http://localhost:5000/"
+      "applicationUrl": "http://0.0.0.0:5000/"
     }
   }
 }

samples/ChatRoom/README.md

@@ -68,6 +68,14 @@ dotnet user-secrets set Azure:SignalR:ConnectionString "<your connection string>
 dotnet run
 ```
 
+## Quick Deploy via Docker image
+You can also deploy this sample via existing docker image
+
+```
+docker run -e Azure__SignalR__ConnectionString="<signalr-connection-string>" \
+           -p 5000:80 mcr.microsoft.com/signalrsamples/chatroom:latest
+```
+
 When you open http://localhost:5000, you can see the application runs as usual, just instead of hosting a SignalR runtime by itself, it connects to the SignalR service running on Azure.
 
 In this sample, you have learned how to use Azure SignalR Service to replace your self-hosted SignalR runtime. But you still need a web server to host your hub logic. In the next tutorial you'll learn how to use other Azure services to host your hub logic so you can get everything running in the cloud.

samples/ChatRoomLocal/ChatRoomLocal.csproj

@@ -1,6 +1,6 @@
 <Project Sdk="Microsoft.NET.Sdk.Web">
   <PropertyGroup>
-    <TargetFramework>netcoreapp3.1</TargetFramework>
+    <TargetFramework>net6.0</TargetFramework>
     <UserSecretsId>chatroom</UserSecretsId>
     <RootNamespace>Microsoft.Azure.SignalR.Samples.ChatRoom</RootNamespace>
   </PropertyGroup>

samples/ChatRoomLocal/Dockerfile

@@ -0,0 +1,6 @@
+FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
+WORKDIR /src/ChatRoomLocal
+
+COPY ./. ./
+RUN dotnet restore && dotnet build
+ENTRYPOINT ["bash", "-c", "dotnet run --urls http://0.0.0.0:80"]

samples/ChatRoomLocal/Properties/launchSettings.json

@@ -18,7 +18,7 @@
     "ChatRoomLocal": {
       "commandName": "Project",
       "launchBrowser": true,
-      "applicationUrl": "https://localhost:5001;http://localhost:5000",
+      "applicationUrl": "http://0.0.0.0:5000",
       "environmentVariables": {
         "ASPNETCORE_ENVIRONMENT": "Development"
       }

samples/ChatRoomLocal/README.md

@@ -138,6 +138,15 @@ dotnet run
 
 > You can also use `dotnet watch run` to watch and reload the code changes.
 
+
+## Quick Deploy via Docker image
+You can also deploy this sample via existing docker image
+
+```
+docker run -e Azure__SignalR__ConnectionString="<signalr-connection-string>" \
+           -p 5000:80 mcr.microsoft.com/signalrsamples/chatroomlocal:latest
+```
+
 Open http://localhost:5000, and you'll see the chat room running on your local machine.
 
 In this sample you have learned the basics of SignalR and how to use it to build a chat room application.

samples/ReliableChatRoom/.gitignore

@@ -2,4 +2,3 @@ bin/
 obj/
 .vs/
 **.csproj.user
-*.sln

samples/ReliableChatRoom/Dockerfile

@@ -0,0 +1,6 @@
+FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
+WORKDIR /src/AdvancedChatRoom
+
+COPY ./. ./
+RUN dotnet restore && dotnet build
+ENTRYPOINT ["bash", "-c", "dotnet run --ConnectionStrings:AzureStorage $STORAGE_CONN_STRING --urls http://0.0.0.0:80"]

samples/ReliableChatRoom/Properties/launchSettings.json

@@ -21,7 +21,7 @@
       "environmentVariables": {
         "ASPNETCORE_ENVIRONMENT": "Development"
       },
-      "applicationUrl": "http://localhost:5000/"
+      "applicationUrl": "http://0.0.0.0:5000/"
     }
   }
 }

samples/ReliableChatRoom/README.md

@@ -52,6 +52,16 @@ dotnet user-secrets set ConnectionStrings:AzureStorage "<Your connection string>
 dotnet run
 ```
 
+## Quick Deploy via Docker image
+You can also deploy this sample via existing docker image
+
+```
+docker run -e Azure__SignalR__ConnectionString="<signalr-connection-string>" \
+           -e STORAGE_CONN_STRING="<storage-connection-string>" \
+		   -p 5000:80 mcr.microsoft.com/signalrsamples/reliablechatroom:latest
+```
+
+
 ### Use your own database
 
 If you want to use your own database to store the messages and sessions, you should create a class which implements [ISessionHandler](./SessionHandler/ISessionHandler.cs) and another one implementing [IMessageHandler](./MessageHandler/IMessageHandler.cs).

samples/ReliableChatRoom/ReliableChatRoom.csproj

@@ -1,6 +1,6 @@
 <Project Sdk="Microsoft.NET.Sdk.Web">
   <PropertyGroup>
-    <TargetFramework>netcoreapp3.1</TargetFramework>
+    <TargetFramework>net6.0</TargetFramework>
     <UserSecretsId>reliablechatroom</UserSecretsId>
     <RootNamespace>Microsoft.Azure.SignalR.Samples.ReliableChatRoom</RootNamespace>
   </PropertyGroup>