Skip to content

Commit 52d3c92

Browse files
committed
Update upgrade command
1 parent 1f77461 commit 52d3c92

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

articles/azure-functions/functions-versions.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -69,16 +69,14 @@ Any function app pinned to `~2.0` continues to run on .NET Core 2.2, which no lo
6969

7070
Azure Functions version 4.x (Preview) is highly backwards compatible to version 3.x. Many apps should be able to safely upgrade to 4.x without any code changes. Be sure to run extensive tests before changing the major version in production apps.
7171

72-
To migrate an app from 3.x to 4.x:
72+
To migrate an app from 3.x to 4.x, set the `FUNCTIONS_EXTENSION_VERSION` application setting to `~4` with the following Azure CLI command:
7373

74-
- Set the `FUNCTIONS_EXTENSION_VERSION` application setting to `~4` with the following Azure CLI command:
74+
```bash
75+
az functionapp config appsettings set --settings FUNCTIONS_EXTENSION_VERSION=~4 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
7576

76-
```bash
77-
az functionapp config appsettings set --settings FUNCTIONS_EXTENSION_VERSION=~4 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
78-
79-
# For Windows function apps only, also enable .NET 6.0 that is needed by the runtime
80-
az functionapp config set --net-framework-version v6.0 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
81-
```
77+
# For Windows function apps only, also enable .NET 6.0 that is needed by the runtime
78+
az functionapp config set --net-framework-version v6.0 -n <APP_NAME> -g <RESOURCE_GROUP_NAME>
79+
```
8280

8381
### Breaking changes between 3.x and 4.x
8482

0 commit comments

Comments
 (0)