Functions using custom extensions work in emulator but fail indexing when deployed (c#, v2.0.12050.0)

[stevedenman]

Following the recent update (2.0.12050.0) I made the change suggested here, using IWebJobsStartup to add extensions, however functions that use these extensions are not being indexed when deployed (works in emulator).

Investigative information

Please provide the following:

• Timestamp:
• Function App version (1.0 or 2.0-beta): 2.0-beta
• Function App name:
• Function name(s) (as appropriate):
• Invocation ID:
• Region: Australia East

Repro steps

Provide the steps required to reproduce the problem:

I deployed to a new function app with a custom extension registered in IWebJobsStartup, but no functions could be indexed;

...
2018-09-04T23:28:17.933 [Information] Host Status: {
"id": "version-two-test",
"state": "Running",
"version": "2.0.12050.0",
"versionDetails": "2.0.12050.0-beta1 Commit hash: 2db3b7e"
}
....
2018-09-04T23:29:22.188 [Information] Starting JobHost
2018-09-04T23:29:22.188 [Information] Starting Host (HostId=version-two-test, InstanceId=8f722119-650d-430b-8e82-9cb9e447e180, Version=2.0.12050.0, ProcessId=5276, AppDomainId=1, Debug=True, FunctionsExtensionVersion=beta)
2018-09-04T23:29:22.230 [Information] Generating 1 job function(s)
2018-09-04T23:29:22.231 [Error] Error indexing method 'TestFunction.Run'
2018-09-04T23:29:22.277 [Warning] Function 'TestFunction.Run' failed indexing and will be disabled.
2018-09-04T23:29:22.277 [Warning] No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. config.UseServiceBus(), config.UseTimers(), etc.).
2018-09-04T23:29:22.277 [Information] Host initialized (89ms)
2018-09-04T23:29:22.278 [Information] Host started (89ms)
2018-09-04T23:29:22.278 [Information] Job host started
...

Expected behavior

All functions are indexed.

Actual behavior

It looks like the custom extensions are not being loaded.

Known workarounds

Related information

Test project here; https://github.com/stevedenman/azure-functions-v2-di/tree/master/AzureFunctionV2DI

[mlankamp]

I'm having the same problems!

[mlankamp]

If you move your extension to a different project, and reference this project the problem is solved. The IWebJobStartup in your functions assembly is ignored in the published extensions.json. (you can verify this in obj/release/pubTmp/bin)

[stevedenman]

Great, thanks @mlankamp, that fixed it. So that's a workaround - who can escalate this so that IWebJobStartup implementations are detected in the main function app binary?

[djmeck]

This is not limited to custom extensions. I am encountering the same issue with the C# CosmosDB binding here: Microsoft.Azure.WebJobs.Extensions.CosmosDB. Unfortunately, there is nothing to move to another project so there is no workaround.

[dbarentine]

I've been running into this as well. The build generates the correct extensions.json in bin\Release\netstandard2.0\bin. So, I created a build target Directory.Build.targets file that can be dropped into the project directory and will copy the correct file at publishing time.

This will copy the correct extensions.json into the publish directory prior to actual deployment/zipping etc...

[hiraldesai]

Thanks @dbarentine for the workaround. Does anyone know if there a fix in the pipeline?

[maadhureave]

If you move your extension to a different project, and reference this project the problem is solved. The IWebJobStartup in your functions assembly is ignored in the published extensions.json. (you can verify this in obj/release/pubTmp/bin)

this worked for me but will this be fixed ?

[mohammedkamranazam]

I've been running into this as well. The build generates the correct extensions.json in bin\Release\netstandard2.0\bin. So, I created a build target Directory.Build.targets file that can be dropped into the project directory and will copy the correct file at publishing time.

This will copy the correct extensions.json into the publish directory prior to actual deployment/zipping etc...

Awesome. Worked like charm for me after 3 days of struggle in making the Function App run on the server. Was running smoothly in my local system, except on the server. Thanks again.