azure-functions-dotnet-worker: Unable to publish an Isolated Azure Function

This is related to https://github.com/dotnet/sdk/issues/30321

An internal team (represented by @gangaken here) is publishing an Isolated Azure Function and experiencing problems during the publish. I can’t upload full details here, but Gangadhar and myself are both available on Teams internally.

The main symptom of the failure is that during the publish of their single functions app, the publish of the ‘internal’ WorkerExtensions.csproj project fails during the _GenerateFunctionsAndCopyContentFiles target while Moveing the runtime assets of the WorkerExtensions project to the publishout/bin directory. According to the binlog, all of the contents of the publishout/bin directory are DoubleWrites - this to me points to a potential source of the problem. Looking at the binlog for one of these DoubleWrite files (for example System.Security.Cryptography.ProtectedData.dll), I see two copies:

  • One during the _CopyResolveDFilesToPublishPreserverNewest Task from the .NET SDK, whose role is to copy publishable outputs to the publish directory
  • One during the _GenerateFunctionsAndCopyContentFiles Task from this project.

That’s about as far as I’ve gotten.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 6
  • Comments: 17 (6 by maintainers)

Most upvoted comments

@magarma yes the changes included a regression. This PR adds it back in: #2347

When will your fix be landed @jviau? It’s been 4+ months to be fixed at this point which is incredibly frustrating when “at random” your CI pipeline fails to build and then you have to wait for the entire pipeline to run again. Clearly this is affecting a number of people given the miriad of linked issues and numbers of people watching these linked issues.

Hello Jacob. Is there any fix for this issue ?

@jviau Any idea on when your fix will make it to a stable release ?

I believe a workaround for this is to build, then publish with --no-build.