Skip to content

Commit 1392cfa

Browse files
authored
Merge pull request #280128 from mattchenderson/netmig-vsc
adding extended toolchain TFM note
2 parents cbd7165 + 2e79c58 commit 1392cfa

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

articles/azure-functions/migrate-dotnet-to-isolated-model.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,8 @@ Use one of the following procedures to update this XML file to run in the isolat
115115

116116
---
117117

118+
Changing your project's target framework might also require changes to parts of your toolchain, outside of project code. For example, in VS Code, you might need to update the `azureFunctions.deploySubpath` extension setting through user settings or your project's `.vscode/settings.json` file. Check for any dependencies on the framework version that may exist outside of your project code, as part of build steps or a CI/CD pipeline.
119+
118120
### Package references
119121

120122
When migrating to the isolated worker model, you need to change the packages your application references.

articles/azure-functions/update-language-versions.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,9 +41,12 @@ Use these steps to update the project on your local computer:
4141

4242
1. Update your project's target framework to the new version. For C# projects, you must update the `<TargetFramework>` element in the `.csproj` file. See [Target frameworks](/dotnet/standard/frameworks) for specifics related to the chosen version.
4343

44+
Changing your project's target framework might also require changes to parts of your toolchain, outside of project code. For example, in VS Code, you might need to update the `azureFunctions.deploySubpath` extension setting through user settings or your project's `.vscode/settings.json` file. Check for any dependencies on the framework version that may exist outside of your project code, as part of build steps or a CI/CD pipeline.
45+
4446
1. Make any updates to your project code that are required by the new .NET version. Check the version's release notes for specifics. You can also use the [.NET Upgrade Assistant](/dotnet/core/porting/upgrade-assistant-overview) to help you update your code in response to changes across major versions.
4547

46-
After you've made those changes, rebuild your project and test it to confirm your app runs as expected.
48+
After you've made those changes, rebuild your project and test it to confirm your app runs as expected.
49+
4750
::: zone-end
4851

4952
### 2. Move to the latest Functions runtime

0 commit comments

Comments
 (0)