Fix pricing info and update System.IO.Pipelines version

Author: chenkennt

Diff for: aspnet-samples/AdvancedChatRoom/ChatSample.AspNet.csproj

@@ -145,7 +145,7 @@
       <HintPath>packages\System.IdentityModel.Tokens.Jwt.5.2.1\lib\net451\System.IdentityModel.Tokens.Jwt.dll</HintPath>
     </Reference>
     <Reference Include="System.IO.Pipelines, Version=4.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51, processorArchitecture=MSIL">
-      <HintPath>packages\System.IO.Pipelines.4.5.0\lib\netstandard2.0\System.IO.Pipelines.dll</HintPath>
+      <HintPath>packages\System.IO.Pipelines.4.5.1\lib\netstandard2.0\System.IO.Pipelines.dll</HintPath>
     </Reference>
     <Reference Include="System.Memory, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51, processorArchitecture=MSIL">
       <HintPath>packages\System.Memory.4.5.0\lib\netstandard2.0\System.Memory.dll</HintPath>

Diff for: aspnet-samples/AdvancedChatRoom/packages.config

@@ -40,7 +40,7 @@
   <package id="Owin" version="1.0" targetFramework="net461" />
   <package id="System.Buffers" version="4.5.0" targetFramework="net461" />
   <package id="System.IdentityModel.Tokens.Jwt" version="5.2.1" targetFramework="net461" />
-  <package id="System.IO.Pipelines" version="4.5.0" targetFramework="net461" />
+  <package id="System.IO.Pipelines" version="4.5.1" targetFramework="net461" />
   <package id="System.Memory" version="4.5.0" targetFramework="net461" />
   <package id="System.Numerics.Vectors" version="4.4.0" targetFramework="net461" />
   <package id="System.Runtime.CompilerServices.Unsafe" version="4.5.0" targetFramework="net461" />

Diff for: aspnet-samples/ChatRoom/README.md

@@ -18,8 +18,8 @@ First let's provision a SignalR service on Azure.
 
    Select a pricing tier. There're two pricing tiers:
 
-   * Free: which can handle 100 connections at the same time and can send and receive one million messages in a month.
-   * Basic: which has 1000 concurrent connections and 75 millions message per month limit for *one unit*. You can scale up to 10 units for a single service instance and you'll be charged by the number of units you use.
+   * Free: which can handle 20 connections at the same time and can send and receive 20,000 messages in a day.
+   * Standard: which has 1000 concurrent connections and one million messages per day limit for *one unit*. You can scale up to 100 units for a single service instance and you'll be charged by the number of units you use.
 
 3. Click "Create", your SignalR service will be created in a few minutes.
 

Diff for: samples/ChatRoom/README.md

@@ -18,8 +18,8 @@ First let's provision a SignalR service on Azure.
 
    Select a pricing tier. There're two pricing tiers:
 
-   * Free: which can handle 100 connections at the same time and can send and receive one million messages in a month.
-   * Basic: which has 1000 concurrent connections and 75 millions message per month limit for *one unit*. You can scale up to 10 units for a single service instance and you'll be charged by the number of units you use.
+   * Free: which can handle 20 connections at the same time and can send and receive 20,000 messages in a day.
+   * Standard: which has 1000 concurrent connections and one million messages per day limit for *one unit*. You can scale up to 100 units for a single service instance and you'll be charged by the number of units you use.
 
 3. Click "Create", your SignalR service will be created in a few minutes.