You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/dotnet-isolated-process-guide.md
+26-13Lines changed: 26 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,11 @@ ms.custom:
17
17
18
18
# Guide for running C# Azure Functions in the isolated worker model
19
19
20
+
> [!NOTE]
21
+
> GA support for .NET 10 is rolling out but is not yet available in all regions. For the latest information about support for .NET 10 in global Azure, see this [tracking thread on GitHub](https://github.com/Azure/azure-functions-dotnet-worker/issues/3152).
22
+
>
23
+
> You can't run .NET 10 apps on Linux in the Consumption plan. To run on Linux, you should instead use the [Flex Consumption plan](./flex-consumption-plan.md).
24
+
20
25
This article is an introduction to working with Azure Functions in .NET, using the isolated worker model. This model allows your project to target versions of .NET independently of other runtime components. For information about specific .NET versions supported, see [supported version](#supported-versions).
21
26
22
27
Use the following links to get started right away building .NET isolated worker model functions.
@@ -65,15 +70,22 @@ The following packages are required to run your .NET functions in an isolated wo
65
70
+[Microsoft.Azure.Functions.Worker]
66
71
+[Microsoft.Azure.Functions.Worker.Sdk]
67
72
68
-
#### Version 2.x
73
+
Minimum versions of these packages are required based on your target .NET version:
69
74
70
-
The 2.x versions of the core packages change the supported frameworks and bring in support for new .NET APIs from these later versions. When you target .NET 9 or later, your app needs to reference version 2.0.0 or later of both packages.
75
+
| .NET version |`Microsoft.Azure.Functions.Worker`|`Microsoft.Azure.Functions.Worker.Sdk`|
| .NET Framework | 1.16.0 or later | 1.11.0 or later |
71
81
72
-
When updating to the 2.x versions, note the following changes:
82
+
#### Version 2.x
83
+
84
+
The 2.x versions of the core packages change the supported frameworks and bring in support for new .NET APIs from these later versions. When updating to the 2.x versions, note the following changes:
73
85
74
86
- Starting with version 2.0.0 of [Microsoft.Azure.Functions.Worker.Sdk]:
75
87
- The SDK includes default configurations for [SDK container builds](/dotnet/core/docker/publish-as-container).
76
-
- The SDK includes support for [`dotnet run`](/dotnet/core/tools/dotnet-run) when the [Azure Functions Core Tools](./functions-develop-local.md) is installed. On Windows, the Core Tools needs to be installed through a mechanism other than NPM.
88
+
- The SDK includes support for [`dotnet run`](/dotnet/core/tools/dotnet-run) when the [Azure Functions Core Tools](./functions-develop-local.md) is installed. On Windows, the Core Tools need to be installed through a mechanism other than NPM.
77
89
- Starting with version 2.0.0 of [Microsoft.Azure.Functions.Worker]:
78
90
- This version adds support for `IHostApplicationBuilder`. Some examples in this guide include tabs to show alternatives using `IHostApplicationBuilder`. These examples require the 2.x versions.
79
91
- Service provider scope validation is included by default if run in a development environment. This behavior matches ASP.NET Core.
@@ -1320,16 +1332,17 @@ While it might be possible to target a given release from a local Functions proj
3. Youcan't run .NET 10 apps on Linux in the Consumption plan. To run on Linux, you should instead use the [Flex Consumption plan](./flex-consumption-plan.md).
>Youcan't run .NET 10 apps on Linux in the Consumption plan. To run on Linux, you should instead use the [Flex Consumption plan](./flex-consumption-plan.md).
1331
1344
1332
-
See [Supportedversions][supported-versions] foralistofgenerallyavailablereleasesthatyoucanuse.
Copy file name to clipboardExpand all lines: includes/functions-dotnet-migrate-v4-versions.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,20 +10,20 @@ ms.author: mahender
10
10
11
11
When you migrate your function app, you have the opportunity to choose the target version of .NET. You can update your C# project to one of the following versions of .NET that are supported by Functions version 4.x:
12
12
13
-
| .NET version |[.NET Official Support Policy] release type |Functions process model<sup>1,2</sup> |
<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, ending with .NET 8. 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).
21
21
22
22
<sup>2</sup> Support ends for the in-process model on November 10, 2026. For more information, see [this support announcement](https://aka.ms/azure-functions-retirements/in-process-model). For continued full support, you should [migrate your apps to the isolated worker model](../articles/azure-functions/migrate-dotnet-to-isolated-model.md).
23
23
24
-
<sup>3</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.
24
+
<!-- <sup>3</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.-->
25
25
26
-
<sup>4</sup> .NET 9 previously had an expected end-of-support date of May 12, 2026. During the .NET 9 service window, the .NET team extended support for STS versions to 24 months, starting with .NET 9. For more information, see [the blog post](https://devblogs.microsoft.com/dotnet/dotnet-sts-releases-supported-for-24-months/).
26
+
<sup>3</sup> .NET 9 previously had an expected end-of-support date of May 12, 2026. During the .NET 9 service window, the .NET team extended support for STS versions to 24 months, starting with .NET 9. For more information, see [the blog post](https://devblogs.microsoft.com/dotnet/dotnet-sts-releases-supported-for-24-months/).
27
27
28
28
[.NET Official Support Policy]: https://dotnet.microsoft.com/platform/support/policy
<sup>1</sup> .NET 6 was previously supported on both models but reached the [end of official support] on November 12, 2024. .NET 7 was previously supported on the isolated worker model but reached the [end of official support] on May 14, 2024.
| .NET 10 | GA |[November 14, 2028][dotnet-policy].|
57
+
| .NET 9 | GA |[November 10, 2026][dotnet-policy]<sup>1</sup>|
58
+
| .NET 8 | GA |[November 10, 2026][dotnet-policy]|
59
+
| .NET Framework 4.8.1 | GA | See [.NET Framework Support Policy][dotnet-framework-policy]. |
60
60
61
61
<sup>1</sup> .NET 9 previously had an expected end-of-support date of May 12, 2026. During the .NET 9 service window, the .NET team extended support for STS versions to 24 months, starting with .NET 9. For more information, see [the blog post](https://devblogs.microsoft.com/dotnet/dotnet-sts-releases-supported-for-24-months/).
0 commit comments