Merge pull request #215093 from ggailey777/melony

[Functions] .NET migration guides and isolated worker clean-up

Author: v-regandowner

.openpublishing.publish.config.json

@@ -164,6 +164,12 @@
       "branch": "dev",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "functions-quickstart-templates-v1",
+      "url": "https://github.com/Azure/azure-functions-templates",
+      "branch": "v1.x",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azure-functions-samples-java",
       "url": "https://github.com/Azure-Samples/azure-functions-samples-java",

articles/azure-functions/TOC.yml

@@ -268,11 +268,13 @@
       items: 
         - name: In-process
           href: functions-dotnet-class-library.md
-        - name: Isolated process 
+        - name: Isolated worker process 
           displayName: .NET isolated, .NET 5
           href: dotnet-isolated-process-guide.md
         - name: Script (.csx)
           href: functions-reference-csharp.md
+        - name: Execution mode comparison
+          href: dotnet-isolated-in-process-differences.md
     - name: F#
       href: functions-reference-fsharp.md
     - name: JavaScript
@@ -295,6 +297,7 @@
           items:
             - name: Develop and debug locally
               href: functions-develop-local.md
+              displayName: local.settings.json
             - name: Visual Studio Code development
               href: functions-develop-vs-code.md
               displayName: VS Code, VS
@@ -422,6 +425,12 @@
           href: ../availability-zones/migrate-functions.md?toc=%2fazure%2fazure-functions%2ftoc.json
         - name: Work with legacy Functions Proxies
           href: legacy-proxies.md  
+    - name: Migrate
+      items:
+        - name: Migrate v3.x to v4.x
+          href: migrate-version-3-version-4.md
+        - name: Migrate v1.x to v4.x
+          href: migrate-version-1-version-4.md
     - name: Monitor
       items:
         - name: Monitor function apps with Azure Monitor

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

@@ -119,7 +119,7 @@ The return object is an [ActionResult](/dotnet/api/microsoft.aspnetcore.mvc.acti
 
 # [Isolated process](#tab/isolated-process)
 
-*HttpExample.cs* contains a `Run` method that receives request data in the `req` variable is an [HttpRequestData](/dotnet/api/microsoft.azure.functions.worker.http.httprequestdata) object that's decorated with the **HttpTriggerAttribute**, which defines the trigger behavior. Because of the isolated process model,    `HttpRequestData` is a representation of the actual `HttpRequest`, and not the request object itself.
+*HttpExample.cs* contains a `Run` method that receives request data in the `req` variable is an [HttpRequestData](/dotnet/api/microsoft.azure.functions.worker.http.httprequestdata) object that's decorated with the **HttpTriggerAttribute**, which defines the trigger behavior. Because of the isolated worker process model,    `HttpRequestData` is a representation of the actual `HttpRequest`, and not the request object itself.
 
 :::code language="csharp" source="~/functions-docs-csharp/http-trigger-isolated/HttpExample.cs":::
 

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

@@ -15,7 +15,7 @@ adobe-target-content: ./create-first-function-vs-code-csharp-ieux
 
 In this article, you use Visual Studio Code 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.0. There's also a [CLI-based version](create-first-function-cli-csharp.md) of this article.
 
-By default, this article shows you how to create C# functions that run [in the same process as the Functions host](functions-dotnet-class-library.md). These _in-process_ C# functions are only supported on Long Term Support (LTS) versions of .NET, such as .NET 6. To create C# functions on .NET 6 that can also run on [other supported versions](functions-versions.md) for Azure functions [in an isolated process](dotnet-isolated-process-guide.md). 
+By default, this article shows you how to create C# functions that run [in the same process as the Functions host](functions-dotnet-class-library.md). These _in-process_ C# functions are only supported on Long Term Support (LTS) versions of .NET, such as .NET 6. To create C# functions on .NET 6 that can also run on [other supported versions](functions-versions.md) for Azure functions [in an isolated worker process](dotnet-isolated-process-guide.md). 
 
 Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
 

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

@@ -0,0 +1,53 @@
+---
+title: Differences between in-process and isolate worker process .NET Azure Functions
+description: Compares features and functionality differences between running .NET Functions in-process or as an isolated worker process. 
+ms.service: azure-functions
+ms.topic: conceptual 
+ms.date: 09/29/2022
+recommendations: false
+#Customer intent: As a developer, I need to understand the differences between running in-process and running in an isolated worker process so that I can choose the best process model for my functions.
+---
+
+# Differences between in-process and isolate worker process .NET Azure Functions
+
+Functions supports two process models for .NET class library functions:
+
+[!INCLUDE [functions-dotnet-execution-model](../../includes/functions-dotnet-execution-model.md)] 
+
+This article describes the current state of the functional and behavioral differences between the two models.
+
+## Execution mode comparison table 
+
+Use the following table to compare feature and functional differences between the two models:
+
+| Feature/behavior |  In-process<sup>3</sup> | Isolated worker process  |
+| ---- | ---- | ---- |
+| .NET versions | Long Term Support (LTS) versions<br/>(.NET 6.0) | All supported versions + .NET Framework<br/>(.NET 6.0, .NET 7.0 (Preview), .NET Framework 4.8 (GA)) |
+| 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 (public preview)](https://github.com/microsoft/durabletask-dotnet#usage-with-azure-functions) | 
+| Model types exposed by bindings | Simple types<br/>JSON serializable types<br/>Arrays/enumerations<br/>Service SDK types such as [BlobClient]<br/>`IAsyncCollector` (for output bindings) | Simple types<br/>JSON serializable types<br/>Arrays/enumerations |
+| HTTP trigger model types| [HttpRequest]/[ObjectResult] | [HttpRequestData]/[HttpResponseData] |
+| Output binding interaction | Return values (single output only)<br/>`out` parameters<br/>`IAsyncCollector` | Return values (expanded model with single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)) |
+| Imperative bindings<sup>1</sup>  | [Supported](functions-dotnet-class-library.md#binding-at-runtime) | Not supported |
+| Dependency injection | [Supported](functions-dotnet-dependency-injection.md)  | [Supported](dotnet-isolated-process-guide.md#dependency-injection) |
+| Middleware | Not supported | [Supported](dotnet-isolated-process-guide.md#middleware) |
+| Logging | [ILogger] passed to the function<br/>[ILogger&lt;T&gt;] via dependency injection | [ILogger]/[ILogger&lt;T&gt;] obtained from [FunctionContext] or via [dependency injection](dotnet-isolated-process-guide.md#dependency-injection)|
+| Application Insights dependencies | [Supported](functions-monitoring.md#dependencies) | [Supported (public preview)](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.ApplicationInsights) |
+| Cancellation tokens | [Supported](functions-dotnet-class-library.md#cancellation-tokens) | [Supported](dotnet-isolated-process-guide.md#cancellation-tokens) |
+| Cold start times<sup>2</sup> | (Baseline) | Additionally includes process launch |
+| ReadyToRun | [Supported](functions-dotnet-class-library.md#readytorun) | [Supported](dotnet-isolated-process-guide.md#readytorun) | 
+
+<sup>1</sup> When you need to interact with a service using parameters determined at runtime, using the corresponding service SDKs directly is recommended over using imperative bindings. The SDKs are less verbose, cover more scenarios, and have advantages for error handling and debugging purposes. This recommendation applies to both models.
+
+<sup>2</sup> Cold start times may be additionally impacted on Windows when using some preview versions of .NET due to just-in-time loading of preview frameworks. This applies to both the in-process and out-of-process models but may be noticeable when comparing across different versions. This delay for preview versions isn't present on Linux plans.
+
+<sup>3</sup> C# Script functions also run in-process and use the same libraries as in-process class library functions. For more information, see the [Azure Functions C# script (.csx) developer reference](functions-reference-csharp.md). 
+
+## Next steps
+
+To learn more, see:
+
++ [Develop .NET class library functions](functions-dotnet-class-library.md)
++ [Develop .NET isolated worker process functions](dotnet-isolated-process-guide.md)
+