Merge pull request #279654 from cephalin/corerefresh2

Update to 8.0, add codespaces, AZD, and Copilot

Author: JamesJBarnett

.openpublishing.publish.config.json

@@ -986,6 +986,12 @@
       "branch": "main",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "msdocs-app-service-sqldb-dotnetcore",
+      "url": "https://github.com/Azure-Samples/msdocs-app-service-sqldb-dotnetcore",
+      "branch": "main",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azuresignalr-samples",
       "url": "https://github.com/aspnet/AzureSignalR-samples",

articles/app-service/app-service-web-configure-tls-mutual-auth.md

@@ -26,7 +26,7 @@ To set up your app to require client certificates:
 
 1. From the left navigation of your app's management page, select **Configuration** > **General Settings**.
 
-1. Set **Client certificate mode** to **Require**. Click **Save** at the top of the page.
+1. Set **Client certificate mode** to **Require**. Select **Save** at the top of the page.
 
 ### [Azure CLI](#tab/azurecli)
 To do the same with Azure CLI, run the following command in the [Cloud Shell](https://shell.azure.com):
@@ -55,7 +55,7 @@ resource appService 'Microsoft.Web/sites@2020-06-01' = {
 }
 ```
 
-### [ARM](#tab/arm)
+### [ARM template](#tab/arm)
 
 For ARM templates, modify the properties `clientCertEnabled`, `clientCertMode`, and `clientCertExclusionPaths`. A sample ARM template snippet is provided for you:
 
@@ -88,25 +88,25 @@ When you enable mutual auth for your application, all paths under the root of yo
 
 1. From the left navigation of your app's management page, select **Configuration** > **General Settings**.
 
-1. Next to **Certificate exclusion paths**, click the edit icon.
+1. Next to **Certificate exclusion paths**, select the edit icon.
 
-1. Click **New path**, specify a path, or a list of paths separated by `,` or `;`, and click **OK**.
+1. Select **New path**, specify a path, or a list of paths separated by `,` or `;`, and select **OK**.
 
-1. Click **Save** at the top of the page.
+1. Select **Save** at the top of the page.
 
-In the following screenshot, any path for your app that starts with `/public` does not request a client certificate. Path matching is case-insensitive.
+In the following screenshot, any path for your app that starts with `/public` doesn't request a client certificate. Path matching is case-insensitive.
 
 ![Certificate Exclusion Paths][exclusion-paths]
 
 ## Access client certificate
 
-In App Service, TLS termination of the request happens at the frontend load balancer. When forwarding the request to your app code with [client certificates enabled](#enable-client-certificates), App Service injects an `X-ARR-ClientCert` request header with the client certificate. App Service does not do anything with this client certificate other than forwarding it to your app. Your app code is responsible for validating the client certificate.
+In App Service, TLS termination of the request happens at the frontend load balancer. When App Service forwards the request to your app code with [client certificates enabled](#enable-client-certificates), it injects an `X-ARR-ClientCert` request header with the client certificate. App Service doesn't do anything with this client certificate other than forwarding it to your app. Your app code is responsible for validating the client certificate.
 
 For ASP.NET, the client certificate is available through the **HttpRequest.ClientCertificate** property.
 
 For other application stacks (Node.js, PHP, etc.), the client cert is available in your app through a base64 encoded value in the `X-ARR-ClientCert` request header.
 
-## ASP.NET 5+, ASP.NET Core 3.1 sample
+## ASP.NET Core sample
 
 For ASP.NET Core, middleware is provided to parse forwarded certificates. Separate middleware is provided to use the forwarded protocol headers. Both must be present for forwarded certificates to be accepted. You can place custom certificate validation logic in the [CertificateAuthentication options](/aspnet/core/security/authentication/certauth).
 
@@ -241,12 +241,12 @@ public class Startup
             private bool IsValidClientCertificate()
             {
                 // In this example we will only accept the certificate as a valid certificate if all the conditions below are met:
-                // 1. The certificate is not expired and is active for the current time on server.
+                // 1. The certificate isn't expired and is active for the current time on server.
                 // 2. The subject name of the certificate has the common name nildevecc
                 // 3. The issuer name of the certificate has the common name nildevecc and organization name Microsoft Corp
                 // 4. The thumbprint of the certificate is 30757A2E831977D8BD9C8496E4C99AB26CB9622B
                 //
-                // This example does NOT test that this certificate is chained to a Trusted Root Authority (or revoked) on the server 
+                // This example doesn't test that this certificate is chained to a Trusted Root Authority (or revoked) on the server 
                 // and it allows for self signed certificates
                 //
 
@@ -344,7 +344,7 @@ export class AuthorizationHandler {
 
 ## Java sample
 
-The following Java class encodes the certificate from `X-ARR-ClientCert` to an `X509Certificate` instance. `certificateIsValid()` validates that the certificate's thumbprint matches the one given in the constructor and that certificate has not expired.
+The following Java class encodes the certificate from `X-ARR-ClientCert` to an `X509Certificate` instance. `certificateIsValid()` validates that the certificate's thumbprint matches the one given in the constructor and that certificate hasn't expired.
 
 
 ```java
@@ -384,16 +384,16 @@ public class ClientCertValidator {
 
     /**
      * Check that the certificate's thumbprint matches the one given in the constructor, and that the
-     * certificate has not expired.
-     * @return True if the certificate's thumbprint matches and has not expired. False otherwise.
+     * certificate hasn't expired.
+     * @return True if the certificate's thumbprint matches and hasn't expired. False otherwise.
      */
     public boolean certificateIsValid() throws NoSuchAlgorithmException, CertificateEncodingException {
         return certificateHasNotExpired() && thumbprintIsValid();
     }
 
     /**
      * Check certificate's timestamp.
-     * @return Returns true if the certificate has not expired. Returns false if it has expired.
+     * @return Returns true if the certificate hasn't expired. Returns false if it has expired.
      */
     private boolean certificateHasNotExpired() {
         Date currentTime = new java.util.Date();

articles/app-service/configure-language-dotnetcore.md

@@ -60,10 +60,10 @@ Set the target framework in the project file for your ASP.NET Core project. For
 
 ::: zone pivot="platform-linux"
 
-Run the following command in the [Cloud Shell](https://shell.azure.com) to set the .NET Core version to 3.1:
+Run the following command in the [Cloud Shell](https://shell.azure.com) to set the .NET Core version to 8.0:
 
 ```azurecli-interactive
-az webapp config set --name <app-name> --resource-group <resource-group-name> --linux-fx-version "DOTNETCORE|3.1"
+az webapp config set --name <app-name> --resource-group <resource-group-name> --linux-fx-version "DOTNETCORE|8.0"
 ```
 
 ::: zone-end
@@ -79,7 +79,7 @@ If you deploy your app using Git, or zip packages [with build automation enabled
 1. Run `dotnet publish` to build a binary for production.
 1. Run custom script if specified by `POST_BUILD_SCRIPT_PATH`.
 
-`PRE_BUILD_COMMAND` and `POST_BUILD_COMMAND` are environment variables that are empty by default. To run pre-build commands, define `PRE_BUILD_COMMAND`. To run post-build commands, define `POST_BUILD_COMMAND`.
+`PRE_BUILD_COMMAND` and `POST_BUILD_COMMAND` are environment variables that are empty by default. To run prebuild commands, define `PRE_BUILD_COMMAND`. To run post-build commands, define `POST_BUILD_COMMAND`.
 
 The following example specifies the two variables to a series of commands, separated by commas.
 
@@ -176,7 +176,7 @@ For more information on troubleshooting ASP.NET Core apps in App Service, see [T
 
 ## Get detailed exceptions page
 
-When your ASP.NET Core app generates an exception in the Visual Studio debugger, the browser displays a detailed exception page, but in App Service that page is replaced by a generic **HTTP 500** error or **An error occurred while processing your request.** message. To display the detailed exception page in App Service, Add the `ASPNETCORE_ENVIRONMENT` app setting to your app by running the following command in the <a target="_blank" href="https://shell.azure.com" >Cloud Shell</a>.
+When your ASP.NET Core app generates an exception in the Visual Studio debugger, the browser displays a detailed exception page, but in App Service that page is replaced by a generic **HTTP 500** or **An error occurred while processing your request.** To display the detailed exception page in App Service, Add the `ASPNETCORE_ENVIRONMENT` app setting to your app by running the following command in the <a target="_blank" href="https://shell.azure.com" >Cloud Shell</a>.
 
 ```azurecli-interactive
 az webapp config appsettings set --name <app-name> --resource-group <resource-group-name> --settings ASPNETCORE_ENVIRONMENT="Development"