blocks|key|268400|text|在进行完整的项目搜索时，我们发现VS代码本身存储在其.vscode目录中，即存储在两个文件中:+settings.json和tasks.json。一些配置键值对仍然指向.net核心3.0，也许它们是在我们调试项目时添加的，而当这些是当前框架时。因此，对于从2.2/3.0到3.1的迁移，我们需要确保删除对旧框架的引用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|268401|​|268402|📷|atomic|offset|length|268403|268404|268405|268406|268407|我们必须显式地将tasks.json从netcoreapp3.0更改为netcoreapp3.1。|ordered-list-item|268408|268409|268410|268411|确保settings.json中的部署路径指向.net核心3.1|268412|268413|268414|PS:在settings.json中，如果您遵循Jeff的文章，则项目运行时将高达3，否则它将主要指向~2。|268415|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/9fac9143b8b63d18c63e9e1bfae604af.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/6a3975da36c7a5167df7e7951406a574.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/87c1ca0709d72aa2826ee26ae8947718.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/f74a63764c40b7a6bada2cc97edd9af5.png^0|0|0|0|1|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0|0|0|1|3|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1E|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1F|8|@]|9|@$G|1G|H|1H|1|1I]]|A|$]]|$1|I|3|C|5|6|7|1J|8|@]|9|@]|A|$]]|$1|J|3|C|5|6|7|1K|8|@]|9|@]|A|$]]|$1|K|3|E|5|F|7|1L|8|@]|9|@$G|1M|H|1N|1|1O]]|A|$]]|$1|L|3|C|5|6|7|1P|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1Q|8|@]|9|@]|A|$]]|$1|P|3|C|5|6|7|1R|8|@]|9|@]|A|$]]|$1|Q|3|E|5|F|7|1S|8|@]|9|@$G|1T|H|1U|1|1V]]|A|$]]|$1|R|3|C|5|6|7|1W|8|@]|9|@]|A|$]]|$1|S|3|T|5|O|7|1X|8|@]|9|@]|A|$]]|$1|U|3|E|5|F|7|1Y|8|@]|9|@$G|1Z|H|20|1|21]]|A|$]]|$1|V|3|C|5|6|7|22|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|23|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15|16|-4]]|17|$5|11|12|13|A|$14|18|16|-4]]|19|$5|11|12|13|A|$14|1A|16|-4]]|1B|$5|11|12|13|A|$14|1C|16|-4]]]]

On doing a full project search, we found that VS Code itself stored [i.e. in its .vscode directory], namely in two files: settings.json and tasks.json. Some config key value pairs still pointed to .net core 3.0 [perhaps these were added during when we were debugging the project when these were the current framework]. So for the migration from 2.2/3.0 to 3.1 we need to to ensure the references to the older frameworks are removed 

<a href="https://i.stack.imgur.com/rKXr9.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/rKXr9.png" alt="setting.json"></a>

<a href="https://i.stack.imgur.com/oxBBa.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/oxBBa.png" alt="tasks.json"></a>

<ol>
<li>We have to explicitly make the changes in tasks.json from netcoreapp3.0 to netcoreapp3.1</li>
</ol>

<a href="https://i.stack.imgur.com/tgav8.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/tgav8.png" alt="Diff changes to tasks.json"></a>

<ol start="2">
<li>Ensure the deploy path in settings.json points to .net core 3.1
<a href="https://i.stack.imgur.com/sYdHN.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/sYdHN.png" alt="Diff changes in settings.json under .vscode"></a></li>
</ol>

PS: In settings.json, project runtime is bumped upto 3 if you have followed Jeff Hollans dev article, otherwise it will mostly point to ~2

We were trying to bump our dotnet version from a mix of .net 2.2 &amp; .net core 3.0 to .net core 3.1 and we followed <a href="https://dev.to/azure/develop-azure-functions-using-net-core-3-0-gcm" rel="nofollow noreferrer">Jeff Holan's Dev post</a> to upgrade which is surmarised as below

To change a project between ~2 and ~3 locally, update the .csproj file of the project and change:
AzureFunctionsVersion from v2 to v3
Microsoft.NET.Sdk.Functions package version to at least 3.0.1
Optionally, you can change to target netcoreapp3.1 if you want to target the latest .NET Core version

But while debugging Azure function project locally in VS Code, it still failed with an error message suggesting that there were still config remnants pointing to 3.0. Anyone encountered this issue?

[<img src="https://i.stack.imgur.com/A4rAE.png" alt="VS Code Azure Function Extension Error code]">

[<img src="https://i.stack.imgur.com/5xT6X.png" alt="csproj + Task Host Run logs]">

Azure Function fails to build when TFM is upgraded from netcoreapp3.0 to netcoreapp3.1

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们试图将我们的dotnet版本从.net 2.2 & .net核心3.0混合到.net核心3.1，然后按照进行升级，如下所示若要在本地将项目更改为~2至~3，请更新项目的.csproj文件并将: AzureFunctionsVersion从v2改为v3 Microsoft.NET.Sdk.Functions包版本至少为3.0.1，如果要针对最新的.NET核心版本，可以选择更改为目标netcore

问当TFM从netcoreapp3.0升级到netcoreapp3.1时，Azure函数无法构建
EN

回答 1

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当TFM从netcoreapp3.0升级到netcoreapp3.1时，Azure函数无法构建EN