New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[V2] Reference assemblies in bin
which are created by registering binding extensions
#3637
Comments
It happened in V2 HttpTrigger Template when I manually add SendGrid to output. |
This is still an issue. Had the same issue with EventHubs:
|
This is fixed now. |
|
I find we have to create storage(blob/queue) trigger, i.e. install storage extensions to use syntax like #r "AssemblyName" to reference assembly under
D:\home\site\wwwroot\bin
.Repro steps
Create a v2 c# eventhub trigger in portal, install eventhub extensions as required. Confirm installation succeeded as I see assemblies( include
Microsoft.Azure.EventHubs.dll
) in bin folder.use code below.
Got compilation error as below
Change
#r "Microsoft.Azure.EventHubs"
to#r "../bin/Microsoft.Azure.EventHubs.dll"
, then compilation succeeded.In same function app ,create a queue trigger.(storage extensions installed)
Go back to eventhub trigger and use
#r "Microsoft.Azure.EventHubs"
again, this time compilation succeeded and code works fine.To avoid cache or something similar, repeat these steps and repro it in several new Function apps.
Another example is v2 sendgrid template. The template uses queuetrigger(i.e. storage extensions installed) and
#r "SendGrid"
works. But if the whole function app doesn't install storage extensions, like a time trigger with SendGrid output, we have to use#r "../bin/SendGrid.dll"
Don't understand how this happened, did I miss sth?
The text was updated successfully, but these errors were encountered: