我无法在此处向类似问题添加辅助或评论:
升级到VS2022 17.1.4
无论如何,我的问题与上述问题有关。 2022将安装了以下Nuget软件包。每当我添加Azure队列触发功能类时,这些软件包似乎相互冲突。当我添加类时,第一个软件包(DurableTask)在解决方案资源管理器中丢失,当我删除该类包时,该软件包重新出现。
Microsoft.Azure.WebJobs.Extensions.DurableTask (2.7.2) -- this goes missing and comes back depending on whether the Storage package is being used of not.
Microsoft.Azure.WebJobs.Extensions.Storage (4.0.5) -- QueueTrigger uses this package.
Microsoft.Extensions.Configuration.UserSecrets (6.0.1)
Microsoft.NET.Sdk.Functions (4.1.1)
为什么会发生这种情况?谁能帮忙吗?
欢呼,亨克。
I am unable to add an adjunct or comment to the similar question here:
Working Durable Functions Project no longer works locally after upgrading to VS2022 17.1.4
In any case, my question is related to the above question. I have the latest v4 Azure Functions Core Tools installed and I am having trouble with an Azure Durable Function project in Visual Studio 2022 which has the following NuGet packages installed. The packages appear to conflict with each other whenever I add an Azure Queue Trigger Function class. When I do add the class, the first package (DurableTask) goes missing in the solution explorer and when I delete that class the package reappears.
Microsoft.Azure.WebJobs.Extensions.DurableTask (2.7.2) -- this goes missing and comes back depending on whether the Storage package is being used of not.
Microsoft.Azure.WebJobs.Extensions.Storage (4.0.5) -- QueueTrigger uses this package.
Microsoft.Extensions.Configuration.UserSecrets (6.0.1)
Microsoft.NET.Sdk.Functions (4.1.1)
Why does this happen? Can anyone help with this?
Cheers, Henk.
发布评论
评论(1)
我们在本地尝试了同样的尝试,并能够通过跟随解决方法来成功调试它。
我们使用您的配置创建了简单的耐用功能,但无法获得相同的问题。
.csproj
文件 -输出屏幕截图供参考: -
注意: - 确保您只有一个
runtime runtime 安装在本地(即V4)中。并尝试在本地和开放的Visual Studio中重新启动Visual Studio并开始存储模拟器/Azurite和测试。
azure untime runtime runtime
runtime有关更多信息,请参阅以下链接: -
类似的问题讨论 @ | >
microsoft文档 | 开发Azure函数并使用VS 添加绑定。
We have tried the same in our local and able to debug it successfully by following workaround.
We have created simple durable function with your configuration but unable to get the same issue .
.csproj
file -OUTPUT SCREENSHOT FOR REFERENCE:-


NOTE:- Make sure that you have only one
Azure function runtime
installed in local (i.e v4 ) . And try to restart visual studio and start storage emulator/Azurite in local and open visual studio and test.For more information please refer the below links:-
Similar issue discussion @ |Github
MICROSOFT DOCUMENTATION|CREATE DURABLE FUNCTION & Develop Azure function and add binding using VS.