Merge pull request #252809 from mattchenderson/net8win

prmerger-automator[bot] · web-flow · commit 464b5ddec96c · 2023-09-27T22:10:11.000Z
removing Linux restriction for .NET 8 in Functions
diff --git a/articles/azure-functions/dotnet-isolated-in-process-differences.md b/articles/azure-functions/dotnet-isolated-in-process-differences.md
@@ -49,7 +49,7 @@ 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.
+<sup>6</sup> The isolated worker model supports .NET 8 [as a preview](./dotnet-isolated-process-guide.md#preview-net-versions). For information about .NET 8 plans, including future options for the in-process model, see the [Azure Functions Roadmap Update post](https://aka.ms/azure-functions-dotnet-roadmap).
 
 [HttpRequest]: /dotnet/api/microsoft.aspnetcore.http.httprequest
 [IActionResult]: /dotnet/api/microsoft.aspnetcore.mvc.iactionresult
diff --git a/articles/azure-functions/dotnet-isolated-process-guide.md b/articles/azure-functions/dotnet-isolated-process-guide.md
@@ -664,6 +664,38 @@ After the debugger is attached, the process execution resumes, and you'll be abl
 
 Because your isolated worker process app runs outside the Functions runtime, you need to attach the remote debugger to a separate process. To learn more about debugging using Visual Studio, see [Remote Debugging](functions-develop-vs.md?tabs=isolated-process#remote-debugging).
 
+## Preview .NET versions
+
+Azure Functions currently can be used with the following preview versions of .NET:
+
+| Operating system | .NET preview version |
+| - | - |
+| Windows | .NET 8 Preview 7 | 
+| Linux | .NET 8 RC1 |
+
+### Using a preview .NET SDK
+
+To use Azure Functions with a preview version of .NET, you need to update your project by:
+
+1. Installing the relevant .NET SDK version in your development
+1. Changing the `TargetFramework` setting in your `.csproj` file
+
+When deploying to a function app in Azure, you also need to ensure that the framework is made available to the app. To do so on Windows, you can use the following CLI command. Replace `<groupName>` with the name of the resource group, and replace `<appName>` with the name of your function app. Replace `<framework>` with the appropriate version string, such as "v8.0".
+
+```azurecli
+az functionapp config set -g <groupName> -n <appName> --net-framework-version <framework>
+```
+
+### Considerations for using .NET preview versions
+
+Keep these considerations in mind when using Functions with preview versions of .NET: 
+
+If you author your functions in Visual Studio, you must use [Visual Studio Preview](https://visualstudio.microsoft.com/vs/preview/), which supports building Azure Functions projects with .NET preview SDKs. You should also ensure you have the latest Functions tools and templates. To update these, navigate to `Tools->Options`, select `Azure Functions` under `Projects and Solutions`, and then click the `Check for updates` button, installing updates as prompted.
+
+During the preview period, your development environment might have a more recent version of the .NET preview than the hosted service. This can cause the application to fail when deployed. To address this, you can configure which version of the SDK to use in [`global.json`](/dotnet/core/tools/global-json). First, identify which versions you have installed using `dotnet --list-sdks` and note the version that matches what the service supports. Then you can run `dotnet new globaljson --sdk-version <sdk-version> --force`, substituting `<sdk-version>` for the version you noted in the previous command. For example, `dotnet new globaljson --sdk-version dotnet-sdk-8.0.100-preview.7.23376.3 --force` will cause the system to use the .NET 8 Preview 7 SDK when building your project.
+
+Note that due to just-in-time loading of preview frameworks, function apps running on Windows may experience increased cold start times when compared against earlier GA versions.
+
 ## Next steps
 
 > [!div class="nextstepaction"]
diff --git a/includes/functions-dotnet-migrate-v4-versions.md b/includes/functions-dotnet-migrate-v4-versions.md
@@ -17,7 +17,7 @@ When you migrate your function app, you have the opportunity to choose the targe
 
 <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/). Within Visual Studio, you must also get the latest toolset and template updates by navigating to `Tools->Options`, selecting `Azure Functions` under `Projects and Solutions`, and then clicking the `Check for updates` button and installing updates as prompted.
+<sup>2</sup> See [Preview .NET versions in the isolated worker model](../articles/azure-functions/dotnet-isolated-process-guide.md#preview-net-versions) for details on support, current restrictions, and instructions for using the preview version.
 
 [.NET Official Support Policy]: https://dotnet.microsoft.com/platform/support/policy
 [netfxpolicy]: https://dotnet.microsoft.com/platform/support/policy/dotnet-framework
diff --git a/includes/functions-dotnet-supported-versions.md b/includes/functions-dotnet-supported-versions.md
@@ -26,7 +26,7 @@ The following table shows the highest level of .NET or .NET Framework that can b
 
 <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/). Within Visual Studio, you must also get the latest toolset and template updates by navigating to `Tools->Options`, selecting `Azure Functions` under `Projects and Solutions`, and then clicking the `Check for updates` button and installing updates as prompted.
+<sup>4</sup> See [Preview .NET versions in the isolated worker model](../articles/azure-functions/dotnet-isolated-process-guide.md#preview-net-versions) for details on support, current restrictions, and instructions for using the preview version.
 
 <sup>5</sup>[Support will end for version 1.x of the Azure Functions runtime on September 14, 2026](https://aka.ms/azure-functions-retirements/hostv1). We highly recommend that you [migrate your apps to version 4.x](../articles/azure-functions/migrate-version-1-version-4.md) for full support.
 
diff --git a/includes/functions-portal-language-support.md b/includes/functions-portal-language-support.md
@@ -13,7 +13,7 @@ The following table shows which languages supported by Functions can run on Linu
 
 | Language | Runtime stack | Linux | Windows | In-portal editing |
 |:--- |:-- |:--|:--- |:--- |
-| [C# (isolated worker model))](../articles/azure-functions/dotnet-isolated-process-guide.md) |.NET|✓ |✓<sup>1</sup> | | 
+| [C# (isolated worker model))](../articles/azure-functions/dotnet-isolated-process-guide.md) |.NET|✓ |✓ | | 
 | [C# (in-process model)](../articles/azure-functions/functions-dotnet-class-library.md)|.NET|✓ |✓ | | 
 | [C# script](../articles/azure-functions/functions-reference-csharp.md) | .NET | ✓ |✓ |✓ |
 | [JavaScript](../articles/azure-functions/functions-reference-node.md?tabs=javascript) | Node.js |✓ |✓ | ✓ |
@@ -23,8 +23,6 @@ The following table shows which languages supported by Functions can run on Linu
 | [TypeScript](../articles/azure-functions/functions-reference-node.md?tabs=typescript) | Node.js |✓ |✓ |  |
 | [Go/Rust/other](../articles/azure-functions/functions-custom-handlers.md) | Custom Handlers |✓ |✓ | |
  
-<sup>1</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).
diff --git a/includes/functions-supported-languages.md b/includes/functions-supported-languages.md
@@ -48,7 +48,7 @@ For more information, see [Develop C# class library functions using Azure Functi
 | [.NET 6 (LTS)](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle) | GA | November 12, 2024 |
 | .NET Framework 4.8 | GA | [See policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-framework)  |
 
-<sup>*</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/).
+<sup>*</sup> See [Preview .NET versions in the isolated worker model](../articles/azure-functions/dotnet-isolated-process-guide.md#preview-net-versions) for details on support, current restrictions, and instructions for using the preview version.
 
 For more information, see [Guide for running C# Azure Functions in an isolated worker process](../articles/azure-functions/dotnet-isolated-process-guide.md).
 
