NuGet based Logic App (Standard) does not build in Visual StudioSee original GitHub issue
I created a new single-tenant Logic App (Standard) using the Logic Apps (Standard) extension in Visual Studio Code. After that, I followed the documentation to migrate to a NuGet package-based (.NET) project.
When I try to build the project with the .NET CLI:
dotnet build -c Debug and
dotnet build -c Release, it builds fine.
However, when I try to build the project within Visual Studio 2019 with the
Debug configuration, I’m getting the following error:
The "DebugSymbolGenerator" task failed unexpectedly. System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=188.8.131.52, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at Microsoft.Azure.Workflows.BuildTasks.DebugSymbolGenerator.DebugSymbolGenerator.LogMessage(String message) at Microsoft.Azure.Workflows.BuildTasks.DebugSymbolGenerator.DebugSymbolGenerator.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
When I try the same with the
Release configuration in Visual Studio, the project builds just fine.
I attached an example solution as a
.zip file that generates the above error:
- Visual Studio 2019 16.10.3
- Microsoft.Azure.Workflows.WebJobs.Extension 1.1.3
- Microsoft.NET.Sdk.Functions 3.0.9
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top GitHub Comments
Thanks for the feedback. Unfortunately we aren’t currently supporting VS development, but it is on the horizon and we will be adding support for it.
@hongzli @kaylumah I would like to add that since our Logic App is part of a solution (.sln) together with other related non-Logic App projects we currently have to unload the Logic App project within Visual Studio in order to build. Also the Visual Studio build task within a Windows-agent based build pipeline in Azure DevOps would not work and requires a separate build with the dotnet cli instead.