Merge pull request #248794 from mattchenderson/func-net8

adding Functions preview for .NET 8

Author: prmerger-automator[bot]

articles/azure-functions/dotnet-isolated-in-process-differences.md

@@ -23,7 +23,7 @@ Use the following table to compare feature and functional differences between th
 
 | Feature/behavior |  In-process<sup>3</sup> | Isolated worker process  |
 | ---- | ---- | ---- |
-| [Supported .NET versions](#supported-versions) | Long Term Support (LTS) versions | Long Term Support (LTS) versions,<br/>Standard Term Support (STS) versions,<br/>.NET Framework |
+| [Supported .NET versions](#supported-versions) | Long Term Support (LTS) versions<sup>6</sup> | Long Term Support (LTS) versions<sup>6</sup>,<br/>Standard Term Support (STS) versions,<br/>.NET Framework |
 | Core packages | [Microsoft.NET.Sdk.Functions](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/) | [Microsoft.Azure.Functions.Worker](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker/)<br/>[Microsoft.Azure.Functions.Worker.Sdk](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Sdk) | 
 | Binding extension packages | [Microsoft.Azure.WebJobs.Extensions.*](https://www.nuget.org/packages?q=Microsoft.Azure.WebJobs.Extensions)  | [Microsoft.Azure.Functions.Worker.Extensions.*](https://www.nuget.org/packages?q=Microsoft.Azure.Functions.Worker.Extensions) | 
 | Durable Functions | [Supported](durable/durable-functions-overview.md) | [Supported](durable/durable-functions-isolated-create-first-csharp.md?pivots=code-editor-visualstudio) (Support does not yet include Durable Entities) | 
@@ -49,6 +49,8 @@ Use the following table to compare feature and functional differences between th
 
 <sup>5</sup> ASP.NET Core types are not supported for .NET Framework.
 
+<sup>6</sup> The isolated worker model supports .NET 8 as a preview, currently for Linux applications only. .NET 8 is not yet available for the in-process model. See the [Azure Functions Roadmap Update post](https://aka.ms/azure-functions-dotnet-roadmap) for more information about .NET 8 plans.
+
 [HttpRequest]: /dotnet/api/microsoft.aspnetcore.http.httprequest
 [IActionResult]: /dotnet/api/microsoft.aspnetcore.mvc.iactionresult
 [HttpRequestData]: /dotnet/api/microsoft.azure.functions.worker.http.httprequestdata?view=azure-dotnet&preserve-view=true 

articles/azure-functions/functions-versions.md

@@ -117,7 +117,7 @@ In Visual Studio, you select the runtime version when you create a project. Azur
 <AzureFunctionsVersion>v4</AzureFunctionsVersion>
 ```
 
-You can also choose `net6.0`, `net7.0`, or `net48` as the target framework if you are using [.NET isolated worker process functions](dotnet-isolated-process-guide.md). Support for `net7.0` and `net48` is currently in preview.
+You can also choose `net6.0`, `net7.0`, `net8.0`, or `net48` as the target framework if you are using [.NET isolated worker process functions](dotnet-isolated-process-guide.md). Support for `net8.0` is currently in preview.
 
 > [!NOTE]
 > Azure Functions 4.x requires the `Microsoft.NET.Sdk.Functions` extension be at least `4.0.0`.

articles/azure-functions/migrate-dotnet-to-isolated-model.md

@@ -49,7 +49,7 @@ On version 4.x of the Functions runtime, your .NET function app targets .NET 6 w
 [!INCLUDE [functions-dotnet-migrate-v4-versions](../../includes/functions-dotnet-migrate-v4-versions.md)]
 
 > [!TIP]
-> **We recommend upgrading to .NET 6 on the isolated worker model.** This provides a quick upgrade path with the longest support window from .NET.
+> **We recommend upgrading to .NET 6 on the isolated worker model.** This provides a quick upgrade path to the fully released version with the longest support window from .NET.
 
 ## Prepare for migration
 

articles/azure-functions/migrate-version-1-version-4.md

@@ -79,7 +79,7 @@ On version 1.x of the Functions runtime, your C# function app targets .NET Frame
 [!INCLUDE [functions-dotnet-migrate-v4-versions](../../includes/functions-dotnet-migrate-v4-versions.md)]
 
 > [!TIP]
-> **Unless your app depends on a library or API only available to .NET Framework, we recommend upgrading to .NET 6 on the isolated worker model.** Many apps on version 1.x target .NET Framework only because that is what was available when they were created. Additional capabilities are available to more recent versions of .NET, and if your app is not forced to stay on .NET Framework due to a dependency, you should upgrade.
+> **Unless your app depends on a library or API only available to .NET Framework, we recommend upgrading to .NET 6 on the isolated worker model.** Many apps on version 1.x target .NET Framework only because that is what was available when they were created. Additional capabilities are available to more recent versions of .NET, and if your app is not forced to stay on .NET Framework due to a dependency, you should upgrade. .NET 6 is the fully released version with the longest support window from .NET. 
 >
 > Migrating to the isolated worker model will require additional code changes as part of this migration, but it will give your app [additional benefits](./dotnet-isolated-in-process-differences.md), including the ability to more easily target future versions of .NET. If you are moving to an LTS or STS version of .NET using the isolated worker model, the [.NET Upgrade Assistant] can also handle many of the necessary code changes for you.
 

articles/azure-functions/migrate-version-3-version-4.md

@@ -38,7 +38,7 @@ On version 3.x of the Functions runtime, your C# function app targets .NET Core
 [!INCLUDE [functions-dotnet-migrate-v4-versions](../../includes/functions-dotnet-migrate-v4-versions.md)]
 
 > [!TIP]
-> **If you're migrating from .NET 5 (on the isolated worker model), we recommend upgrading to .NET 6 on the isolated worker model.** This provides a quick upgrade path with the longest support window from .NET.
+> **If you're migrating from .NET 5 (on the isolated worker model), we recommend upgrading to .NET 6 on the isolated worker model.** This provides a quick upgrade path to the fully released version with the longest support window from .NET.
 >
 > **If you're migrating from .NET Core 3.1 (on the in-process model), we recommend upgrading to .NET 6 on the in-process model.** This provides a quick upgrade path. However, you might also consider upgrading to .NET 6 on the isolated worker model. Switching to the isolated worker model will require additional code changes as part of this migration, but it will give your app [additional benefits](./dotnet-isolated-in-process-differences.md), including the ability to more easily target future versions of .NET. If you are moving to an LTS or STS version of .NET using the isolated worker model, the [.NET Upgrade Assistant] can also handle many of the necessary code changes for you.
 

includes/functions-dotnet-migrate-v4-versions.md

@@ -10,12 +10,15 @@ When you migrate your function app, you have the opportunity to choose the targe
 
 | .NET version | [.NET Official Support Policy] release type |  Functions process model<sup>1</sup> | 
 | --- | --- | --- |
+| .NET 8 (preview<sup>2</sup>) | LTS (preview) | [Isolated worker model] | 
 | .NET 7 | STS (end of support May 14, 2024) |  [Isolated worker model] | 
 | .NET 6 | LTS (end of support November 12, 2024) |  [Isolated worker model],<br/>[In-process model]  | 
 | .NET Framework 4.8 | [See policy][netfxpolicy] | [Isolated worker model] |  
 
 <sup>1</sup> The [isolated worker model] supports Long Term Support (LTS) and Standard Term Support (STS) versions of .NET, as well as .NET Framework. The [in-process model] only supports LTS releases of .NET. For a full feature and functionality comparison between the two models, see [Differences between in-process and isolate worker process .NET Azure Functions](../articles/azure-functions/dotnet-isolated-in-process-differences.md). 
 
+<sup>2</sup> Preview support for .NET 8 function apps is currently limited to Linux applications. To develop using .NET 8 Preview SDKs in Visual Studio, you must use [Visual Studio 2022 Preview](https://visualstudio.microsoft.com/vs/preview/).
+
 [.NET Official Support Policy]: https://dotnet.microsoft.com/platform/support/policy
 [netfxpolicy]: https://dotnet.microsoft.com/platform/support/policy/dotnet-framework
 [Isolated worker model]: ../articles/azure-functions/dotnet-isolated-process-guide.md

includes/functions-dotnet-supported-versions.md

@@ -13,18 +13,20 @@ Versions of the Functions runtime support specific versions of .NET. To learn mo
 >[!NOTE]
 >To learn how to change the Functions runtime version used by your function app, see [view and update the current runtime version](../articles/azure-functions/set-runtime-version.md#view-and-update-the-current-runtime-version).
 
-The following table shows the highest level of .NET Core or .NET Framework that can be used with a specific version of Functions. 
+The following table shows the highest level of .NET or .NET Framework that can be used with a specific version of Functions. 
 
 | Functions runtime version | In-process<br/>([.NET class library](../articles/azure-functions/functions-dotnet-class-library.md)) | Isolated worker process<br/>([.NET Isolated](../articles/azure-functions/dotnet-isolated-process-guide.md)) |
 | ---- | ---- | --- |
-| Functions 4.x | .NET 6.0<sup>1</sup>  | .NET 6.0<sup>1</sup><br/>.NET 7.0 (GA)<sup>2,3</sup><br/>.NET Framework 4.8 (GA)<sup>3</sup> |
+| Functions 4.x | .NET 6.0<sup>1</sup>  | .NET 6.0<sup>1</sup><br/>.NET 7.0<sup>2</sup><br/>.NET Framework 4.8<sup>3</sup><br/>.NET 8.0 (Preview)<sup>4</sup> |
 | Functions 1.x | .NET Framework 4.8 | n/a |
 
 <sup>1</sup> Per the [.NET Official Support Policy], .NET 6 will reach end of support on November 12, 2024.
 
 <sup>2</sup> Per the [.NET Official Support Policy], .NET 7 will reach end of support on May 14, 2024.
 
-<sup>2</sup> Build process also requires [.NET 6 SDK](https://dotnet.microsoft.com/download).
+<sup>3</sup> Build process also requires [.NET 6 SDK](https://dotnet.microsoft.com/download).
+
+<sup>4</sup> Preview support for .NET 8 function apps is currently limited to Linux applications. To develop using .NET 8 Preview SDKs in Visual Studio, you must use [Visual Studio 2022 Preview](https://visualstudio.microsoft.com/vs/preview/).
 
 For the latest news about Azure Functions releases, including the removal of specific older minor versions, monitor [Azure App Service announcements](https://github.com/Azure/app-service-announcements/issues).
 

includes/functions-portal-language-support.md

@@ -14,7 +14,7 @@ The following table shows which languages supported by Functions can run on Linu
 | Language | Runtime stack | Linux | Windows | In-portal editing |
 |:--- |:-- |:--|:--- |:--- |
 | [C# (in-process model)](../articles/azure-functions/functions-dotnet-class-library.md)|.NET|✓ |✓ | | 
-| [C# (isolated process model))](../articles/azure-functions/dotnet-isolated-process-guide.md) |.NET|✓ |✓ | | 
+| [C# (isolated worker model))](../articles/azure-functions/dotnet-isolated-process-guide.md) |.NET|✓ |✓<sup>2</sup> | | 
 | [C# script](../articles/azure-functions/functions-reference-csharp.md) | .NET | ✓ |✓ |✓ |
 | [JavaScript](../articles/azure-functions/functions-reference-node.md?tabs=javascript) | Node.js |✓ |✓ | ✓ |
 | [Python](../articles/azure-functions/functions-reference-python.md)<sup>1</sup> | Python |✓ | |✓ |
@@ -25,6 +25,8 @@ The following table shows which languages supported by Functions can run on Linu
 
 <sup>1</sup> In-portal editing requires your function to be defined in a function.json file. Because the [Python v2 programming model](../articles/azure-functions/functions-reference-python.md?pivots=python-mode-decorators#programming-model) uses Python code decorators instead of function.json to define functions, only the Python v1 programming model is supported for in-portal development.   
 
+<sup>2</sup> The preview for .NET 8 on the isolated worker model currently only supports Linux. All other versions of .NET are supported on Windows.
+
 For more information on operating system and language support, see [Operating system/runtime support](../articles/azure-functions/functions-scale.md#operating-systemruntime).
 
 When in-portal editing isn't available, you must instead [develop your functions locally](../articles/azure-functions/functions-develop-local.md#local-development-environments).

includes/functions-supported-languages.md

@@ -9,15 +9,20 @@ ms.custom: include file
 
 |Language                                 |1.x         |2.x<sup>1</sup> | 3.x<sup>1</sup> | 4.x |
 |-----------------------------------------|------------|---| --- | --- |
-|[C#](../articles/azure-functions/functions-dotnet-class-library.md)|GA (.NET Framework 4.8)|GA (.NET Core 2.1)| GA (.NET Core 3.1)<br/> | GA (.NET 6.0)<br/>[GA (.NET 7.0)](../articles/azure-functions/dotnet-isolated-process-guide.md)<br/>[GA (.NET Framework 4.8)](../articles/azure-functions/dotnet-isolated-process-guide.md) |
+|[C#](../articles/azure-functions/functions-dotnet-class-library.md)|GA (.NET Framework 4.8)|GA (.NET Core 2.1)| GA (.NET Core 3.1)<br/> | GA (.NET 6.0)<br/>[GA (.NET 7.0)][isolated]<br/>[GA (.NET Framework 4.8)][isolated]<br/>[Preview (.NET 8.0)][isolated]<sup>3</sup>  |
 |[JavaScript](../articles/azure-functions/functions-reference-node.md?tabs=javascript)|GA (Node.js 6)|GA (Node.js 10 & 8)| GA (Node.js 14, 12, & 10) | GA (Node.js 18, 16, & 14) |
 |[Java](../articles/azure-functions/functions-reference-java.md)|N/A|GA (Java 8)| GA (Java 11 & 8)| GA (Java 11 & 8) <br/> GA (Java 17)|
 |[PowerShell](../articles/azure-functions/functions-reference-powershell.md) |N/A|N/A|N/A| GA (PowerShell 7.2)|
 |[Python](../articles/azure-functions/functions-reference-python.md#python-version)|N/A|GA (Python 3.7)| GA (Python 3.9, 3.8, 3.7)| Preview (Python 3.11)<br/>GA (Python 3.10, 3.9, 3.8, 3.7) |
 |[TypeScript](../articles/azure-functions/functions-reference-node.md?tabs=typescript)<sup>2</sup> |N/A|GA| GA | GA |
 
 <sup>1</sup> Reached the end of life (EOL) on December 13, 2022. We highly recommend you [migrating your apps to version 4.x](../articles/azure-functions/migrate-version-3-version-4.md) for full support.  
+
 <sup>2</sup> Supported through transpiling to JavaScript.
 
+<sup>3</sup> Preview support for .NET 8 function apps is currently limited to Linux applications. To develop using .NET 8 Preview SDKs in Visual Studio, you must use [Visual Studio 2022 Preview](https://visualstudio.microsoft.com/vs/preview/).
+
 See the language-specific developer guide article for more details about supported language versions.   
 For information about planned changes to language support, see [Azure roadmap](https://azure.microsoft.com/roadmap/?tag=functions).
+
+[isolated]: ../articles/azure-functions/dotnet-isolated-process-guide.md