Skip to content

Commit c3cff4b

Browse files
committed
Fix remaining tab order manually
1 parent 1e90bbc commit c3cff4b

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

includes/functions-vstools-create.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -16,29 +16,27 @@ The Azure Functions project template in Visual Studio creates a C# class library
1616

1717
1. For the **Create a new Azure Functions application** settings, use the values in the following table:
1818

19-
# [In-process model](#tab/in-process)
19+
# [Isolated worker model](#tab/isolated-process)
2020

2121
| Setting | Value | Description |
2222
| ------------ | ------- |----------------------------------------- |
23-
| **.NET version** | **.NET 6** | This value creates a function project that runs in-process with version 4.x of the Azure Functions runtime. Azure Functions 1.x supports the .NET Framework. For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
23+
| **.NET version** | **.NET 6 Isolated** | This value creates a function project that runs in an [isolated worker process](../articles/azure-functions/dotnet-isolated-process-guide.md). For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
2424
| **Function template** | **HTTP trigger** | This value creates a function triggered by an HTTP request. |
2525
| **Storage account (AzureWebJobsStorage)** | **Storage emulator** | 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. |
2626
| **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](../articles/azure-functions/functions-bindings-http-webhook-trigger.md#authorization-keys) and [HTTP and webhook bindings](../articles/azure-functions/functions-bindings-http-webhook.md). |
2727

28-
29-
![Azure Functions project settings](./media/functions-vs-tools-create/functions-project-settings.png)
28+
![Azure Functions project settings](./media/functions-vs-tools-create/functions-project-settings-v4-isolated.png)
3029

31-
# [Isolated worker model](#tab/isolated-process)
30+
# [In-process model](#tab/in-process)
3231

3332
| Setting | Value | Description |
3433
| ------------ | ------- |----------------------------------------- |
35-
| **.NET version** | **.NET 6 Isolated** | This value creates a function project that runs in an [isolated worker process](../articles/azure-functions/dotnet-isolated-process-guide.md). For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
34+
| **.NET version** | **.NET 6** | This value creates a function project that runs in-process with version 4.x of the Azure Functions runtime. Azure Functions 1.x supports the .NET Framework. For more information, see [Azure Functions runtime versions overview](../articles/azure-functions/functions-versions.md). |
3635
| **Function template** | **HTTP trigger** | This value creates a function triggered by an HTTP request. |
3736
| **Storage account (AzureWebJobsStorage)** | **Storage emulator** | 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. |
3837
| **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](../articles/azure-functions/functions-bindings-http-webhook-trigger.md#authorization-keys) and [HTTP and webhook bindings](../articles/azure-functions/functions-bindings-http-webhook.md). |
3938

40-
41-
![Azure Functions project settings](./media/functions-vs-tools-create/functions-project-settings-v4-isolated.png)
39+
![Azure Functions project settings](./media/functions-vs-tools-create/functions-project-settings.png)
4240

4341
---
4442

0 commit comments

Comments
 (0)