A recent update changed the way that private assemblies were being loaded from the bin directory. A side effect of this is that now calls to Assembly.Location return an empty string. Some libraries depend on this, and as such, aren't functioning properly.
While we work on a fix, there are two workarounds:
Workaround 1 -- Move the assembly to a different folder:
Function app settings
Go to App Service Settings
Workaround 2 -- Revert to the previous Functions version:
Configure app settings
avoid issue : Azure/azure-webjobs-sdk-script#1073 by change reference…
… dll location
It also happen on me 6days ago and Workaround 2 completely avoid issue, thank you very much for share!
My situation was here.
Issue fix at my environment with following commit.
Appreciate for advice! Great help.
@guitarrapc thank you for sharing the details! I'm glad the workaround addressed the issue without requiring you to target the previous version.
As mentioned on the Twitter conversation, we'll be addressing this issue. Apologies for the inconvenience.