Updated setup documentation to migrate from functions v2 beta to final

Author: joelhulen

documentation/setup.md

@@ -642,7 +642,7 @@ Therefore we want to create a new product and add to it several APIs.
 
 3.  Re-select the API Management Service to go to detail and click on `APIs`. Click the **Add a new API** and select the `Blank API`. 
 
-**Please note** that, normally the Function App can produce a Swagger file that can be imported directly. But unfortunately for V2 Beta (at the time of this writing), the `API Definitions` feature is not available. 
+**Please note** that, normally the Function App can produce a Swagger file that can be imported directly. But unfortunately for V2 (at the time of this writing), the `API Definitions` feature is not available.
 
 4.  Complete the API Management API creation form for `Drivers` with the following:
 
@@ -658,7 +658,7 @@ Therefore we want to create a new product and add to it several APIs.
 
 5.  Repeat step 4 for the `Trips` and `Passengers` Function Apps. The `Orchestrators` are not exposed to the outside world and hence they should not be added to APIM.
 
-6. For each API we created, we need to design its operations. As noted above, this step will have to be done manually for V2 Beta. Select `Design` and click on **Add operation** for each operation (**please note** that the API operations are listed below so they can be added manually). Complete the operation form as shown here for a sample operation:
+6. For each API we created, we need to design its operations. As noted above, this step will have to be done manually for V2. Select `Design` and click on **Add operation** for each operation (**please note** that the API operations are listed below so they can be added manually). Complete the operation form as shown here for a sample operation:
 
     1. **Display Name**: Enter a name i.e. `Get Driver Locations`.
     2. **Name**: Enter an identifier `get-driver-locations`.
@@ -889,7 +889,7 @@ The reference implementation solution requires several settings for each functio
 | KEY | DESCRIPTION |
 |---|---|
 | APPINSIGHTS_INSTRUMENTATIONKEY | The Application Insights Resource Instrumentation Key. This key is required by the Function App so it knows there is an application insights resource associated with it | 
-| FUNCTIONS_EXTENSION_VERSION | Must be set to `.0.11961-alpha` since the solution uses V2 beta | 
+| FUNCTIONS_EXTENSION_VERSION | Must be set to `~2` since the solution uses V2 | 
 | DocDbApiKey | The Cosmos DB API Key | 
 | DocDbEndpointUri | The Cosmos DB Endpoint URI | 
 | DocDbRideShareDatabaseName | The Cosmos Database i.e. `RideShare` | 
@@ -906,7 +906,7 @@ The reference implementation solution requires several settings for each functio
 | KEY | DESCRIPTION |
 |---|---|
 | APPINSIGHTS_INSTRUMENTATIONKEY | The Application Insights Resource Instrumentation Key. This key is required by the Function App so it knows there is an application insights resource associated with it | 
-| FUNCTIONS_EXTENSION_VERSION | Must be set to `.0.11961-alpha` since the solution uses V2 beta | 
+| FUNCTIONS_EXTENSION_VERSION | Must be set to `~2` since the solution uses V2 | 
 | AzureWebJobsDashboard | The Storage Account Connection String | 
 | AzureWebJobsStorage | The Storage Account Connection String | 
 | DocDbApiKey | The Cosmos DB API Key | 
@@ -928,7 +928,7 @@ The reference implementation solution requires several settings for each functio
 | KEY | DESCRIPTION |
 |---|---|
 | APPINSIGHTS_INSTRUMENTATIONKEY | The Application Insights Resource Instrumentation Key. This key is required by the Function App so it knows there is an application insights resource associated with it | 
-| FUNCTIONS_EXTENSION_VERSION | Must be set to `.0.11961-alpha` since the solution uses V2 beta | 
+| FUNCTIONS_EXTENSION_VERSION | Must be set to `~2` since the solution uses V2 | 
 | AzureWebJobsDashboard | The Storage Account Connection String | 
 | AzureWebJobsStorage | The Storage Account Connection String | 
 | DocDbApiKey | The Cosmos DB API Key | 
@@ -954,7 +954,7 @@ The reference implementation solution requires several settings for each functio
 | KEY | DESCRIPTION |
 |---|---|
 | APPINSIGHTS_INSTRUMENTATIONKEY | The Application Insights Resource Instrumentation Key. This key is required by the Function App so it knows there is an application insights resource associated with it | 
-| FUNCTIONS_EXTENSION_VERSION | Must be set to `.0.11961-alpha` since the solution uses V2 beta | 
+| FUNCTIONS_EXTENSION_VERSION | Must be set to `~2` since the solution uses V2 | 
 | AzureWebJobsDashboard | The Storage Account Connection String | 
 | AzureWebJobsStorage | The Storage Account Connection String | 
 | DocDbApiKey | The Cosmos DB API Key | 
@@ -1384,36 +1384,36 @@ In the `Dockerfiles` folder of the `.NET` source code, there is a `docker` file
 **Drivers**:
 
 ```docker
-FROM microsoft/azure-functions-dotnet-core2.0:v2.0.11961-alpha
+FROM microsoft/azure-functions-dotnet-core2.0:2.0
 
 COPY ./ServerlessMicroservices.FunctionApp.Drivers/bin/Debug/netstandard2.0 /home/site/wwwroot
 ```
 
 **Passengers**:
 
 ```docker
-FROM microsoft/azure-functions-dotnet-core2.0:v2.0.11961-alpha
+FROM microsoft/azure-functions-dotnet-core2.0:2.0
 
 COPY ./ServerlessMicroservices.FunctionApp.Passengers/bin/Debug/netstandard2.0 /home/site/wwwroot
 ```
 
 **Orchestrators**:
 
 ```docker
-FROM microsoft/azure-functions-dotnet-core2.0:v2.0.11961-alpha
+FROM microsoft/azure-functions-dotnet-core2.0:2.0
 
 COPY ./ServerlessMicroservices.FunctionApp.Orchestrators/bin/Debug/netstandard2.0 /home/site/wwwroot
 ```
 
 **Trips**:
 
 ```docker
-FROM microsoft/azure-functions-dotnet-core2.0:v2.0.11961-alpha
+FROM microsoft/azure-functions-dotnet-core2.0:2.0
 
 COPY ./ServerlessMicroservices.FunctionApp.Trips/bin/Debug/netstandard2.0 /home/site/wwwroot
 ```
 
-The `Dockerfile` is straightforward! We base it on the `microsoft/azure-functions-dotnet-core2.0` image with `v2.0.11961-alpha` tag (as it is the current version) and we copy the output of the `bin\<build>\netstandard2.0` to the `wwwroot` of the image.
+The `Dockerfile` is straightforward! We base it on the `microsoft/azure-functions-dotnet-core2.0` image with `v2~2` tag (as it is the current version) and we copy the output of the `bin\<build>\netstandard2.0` to the `wwwroot` of the image.
 
 ### Docker Images
 
@@ -1500,7 +1500,7 @@ properties:
         - "name": "APPINSIGHTS_INSTRUMENTATIONKEY"
           "value": "<your-own>"
         - "name": "FUNCTIONS_EXTENSION_VERSION"
-          "value": "2.0.11961-alpha"
+          "value": "~2"
         - "name": "AzureWebJobsDashboard"
           "value": "<your-own>"
         - "name": "AzureWebJobsStorage"
@@ -1659,7 +1659,7 @@ spec:
         - "name": "APPINSIGHTS_INSTRUMENTATIONKEY"
           "value": "<your-own>"
         - "name": "FUNCTIONS_EXTENSION_VERSION"
-          "value": "2.0.11961-alpha"
+          "value": "~2"
         - "name": "AzureWebJobsDashboard"
           "value": "<your-own>"
         - "name": "AzureWebJobsStorage"
@@ -1720,7 +1720,7 @@ spec:
         - "name": "APPINSIGHTS_INSTRUMENTATIONKEY"
           "value": "<your-own>"
         - "name": "FUNCTIONS_EXTENSION_VERSION"
-          "value": "2.0.11961-alpha"
+          "value": "~2"
         - "name": "AzureWebJobsDashboard"
           "value": "<your-own>"
         - "name": "AzureWebJobsStorage"
@@ -1785,7 +1785,7 @@ spec:
         - "name": "APPINSIGHTS_INSTRUMENTATIONKEY"
           "value": "<your-own>"
         - "name": "FUNCTIONS_EXTENSION_VERSION"
-          "value": "2.0.11961-alpha"
+          "value": "~2"
         - "name": "AzureWebJobsDashboard"
           "value": "<your-own>"
         - "name": "AzureWebJobsStorage"
@@ -1845,7 +1845,7 @@ spec:
         - "name": "APPINSIGHTS_INSTRUMENTATIONKEY"
           "value": "<your-own>"
         - "name": "FUNCTIONS_EXTENSION_VERSION"
-          "value": "2.0.11961-alpha"
+          "value": "~2"
         - "name": "AzureWebJobsDashboard"
           "value": "<your-own>"
         - "name": "AzureWebJobsStorage"