Merge pull request #258717 from mattchenderson/post-sdp

updating quickstarts to .NET 8

Author: prmerger-automator[bot]

Diff for: articles/azure-functions/create-first-function-cli-csharp.md

@@ -15,15 +15,15 @@ adobe-target-content: ./create-first-function-cli-csharp-ieux
 
 In this article, you use command-line tools to create a C# function that responds to HTTP requests. After testing the code locally, you deploy it to the serverless environment of Azure Functions. 
 
-This article creates an HTTP triggered function that runs on .NET 6 in an isolated worker process. For information about .NET versions supported for C# functions, see [Supported versions](dotnet-isolated-process-guide.md#supported-versions). There's also a [Visual Studio Code-based version](create-first-function-vs-code-csharp.md) of this article.
+This article creates an HTTP triggered function that runs on .NET 8 in an isolated worker process. For information about .NET versions supported for C# functions, see [Supported versions](dotnet-isolated-process-guide.md#supported-versions). There's also a [Visual Studio Code-based version](create-first-function-vs-code-csharp.md) of this article.
 
 Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
 
 ## Configure your local environment
 
 Before you begin, you must have the following:
 
-+ [.NET 6.0 SDK](https://dotnet.microsoft.com/download).
++ [.NET 8.0 SDK](https://dotnet.microsoft.com/download).
 
 + One of the following tools for creating Azure resources:
 
@@ -42,7 +42,7 @@ In Azure Functions, a function project is a container for one or more individual
 1. Run the `func init` command, as follows, to create a functions project in a folder named *LocalFunctionProj* with the specified runtime:
 
     ```console
-    func init LocalFunctionProj --worker-runtime dotnet-isolated --target-framework net6.0
+    func init LocalFunctionProj --worker-runtime dotnet-isolated --target-framework net8.0
     ```
  
 

Diff for: articles/azure-functions/create-first-function-vs-code-csharp.md

@@ -9,7 +9,7 @@ ms.custom: devx-track-csharp, mode-ui, vscode-azure-extension-update-complete
 
 # Quickstart: Create a C# function in Azure using Visual Studio Code
 
-This article creates an HTTP triggered function that runs on .NET 6 in an isolated worker process. For information about .NET versions supported for C# functions, see [Supported versions](dotnet-isolated-process-guide.md#supported-versions).
+This article creates an HTTP triggered function that runs on .NET 8 in an isolated worker process. For information about .NET versions supported for C# functions, see [Supported versions](dotnet-isolated-process-guide.md#supported-versions).
 
 There's also a [CLI-based version](create-first-function-cli-csharp.md) of this article.
 
@@ -38,7 +38,7 @@ In this section, you use Visual Studio Code to create a local Azure Functions pr
     |Prompt|Selection|
     |--|--|
     |**Select a language for your function project**|Choose `C#`.|
-    | **Select a .NET runtime** | Choose `.NET 6.0 Isolated (LTS)`.|
+    | **Select a .NET runtime** | Choose `.NET 8.0 Isolated (LTS)`.|
     |**Select a template for your project's first function**|Choose `HTTP trigger`.|
     |**Provide a function name**|Type `HttpExample`.|
     |**Provide a namespace** | Type `My.Functions`. |

Diff for: articles/azure-functions/functions-create-your-first-function-visual-studio.md

@@ -12,7 +12,7 @@ ms.custom: devx-track-csharp, mvc, devcenter, vs-azure, 23113853-34f2-4f, contpe
 
 Azure Functions lets you use Visual Studio to create local C# function projects and then easily publish this project to run in a scalable serverless environment in Azure. If you prefer to develop your C# apps locally using Visual Studio Code, you should instead consider the [Visual Studio Code-based version](create-first-function-vs-code-csharp.md) of this article.
 
-By default, this article shows you how to create C# functions that run on .NET 6 in an [isolated worker process](dotnet-isolated-process-guide.md). Function apps that run in an isolated worker process are supported on all versions of .NET that are supported by Functions. For more information, see [Supported versions](dotnet-isolated-process-guide.md#supported-versions).
+By default, this article shows you how to create C# functions that run on .NET 8 in an [isolated worker process](dotnet-isolated-process-guide.md). Function apps that run in an isolated worker process are supported on all versions of .NET that are supported by Functions. For more information, see [Supported versions](dotnet-isolated-process-guide.md#supported-versions).
 
 In this article, you learn how to:
 
@@ -44,7 +44,7 @@ The Azure Functions project template in Visual Studio creates a C# class library
 
     | Setting      | Value  | Description                      |
     | ------------ |  ------- |----------------------------------------- |
-    | **Functions worker** | **.NET 6.0 Isolated (Long Term Support)** | Your functions run on .NET 6 in an isolated worker process. | 
+    | **Functions worker** | **.NET 8.0 Isolated (Long Term Support)** | Your functions run on .NET 8 in an isolated worker process. | 
     | **Function** | **HTTP trigger** | This value creates a function triggered by an HTTP request. |
     | **Use Azurite for runtime storage account (AzureWebJobsStorage)**  | Enable | Because a function app in Azure requires a storage account, one is assigned or created when you publish your project to Azure. An HTTP trigger doesn't use an Azure Storage account connection string; all other trigger types require a valid Azure Storage account connection string. When you select this option, the [Azurite emulator](../storage/common/storage-use-azurite.md?tabs=visual-studio) is used. |
     | **Authorization level** | **Anonymous** | The created function can be triggered by any client without providing a key. This authorization setting makes it easy to test your new function. For more information about keys and authorization, see [Authorization keys](./functions-bindings-http-webhook-trigger.md#authorization-keys) and [HTTP and webhook bindings](./functions-bindings-http-webhook.md). |