Azure-webjobs-sdk: Beta5 - Method not found: 'FluentBinder<!0> Microsoft.Azure.WebJobs.Host.Config.FluentBindingRule`1.BindToInput(Microsoft.Azure.WebJobs.IAsyncConverter`2<!0,!!0>)'.

[isaiahwilliams]

Please provide a succinct description of the issue.

Repro steps

Provide the steps required to reproduce the problem

1. Develop a custom extension using the Microsoft.Azure..WebJobs version 3.0.0-beta5

2. Initialize the extension using a class that inherits from IExtensionConfigProvider

3. Call context.AddBindingRule().BindToInput(new MyConverter()); in the initialize function

Expected behavior

The extension should execute the function to bind the input attribute.

Actual behavior

Provide a description of the actual behavior observed.

Known workarounds

I have not discovered any work arounds yet.

Related information

Provide any related information

• Package version 3.0.0-beta5

[codepossible]

I have the exact same error. Downgrading to 3.0.0-beta4 resolves the issue for local development. But I cannot deploy the application on to Azure Functions. Same for AddValidator method which gives a warning that it is being deprecated on beta4.

[MV10]

Same here converting some Functions V1 projects to V2. Throws with Functions SDK 1.0.11 or 1.0.12 and webjobs 3.0.0-beta5.

I downgraded the SDK to 1.0.10 to use webjobs beta4. That _does_ run locally, but it turns out that can't be deployed. On Azure the Functions host crashes with: _Method not found: 'Void Microsoft.Azure.WebJobs.Host.Config.FluentBindingRule`1.Bind(Microsoft.Azure.WebJobs.Host.Bindings.IBindingProvider)'._

Edit ... downgraded all the way to SDK 1.0.4 and beta3 (the oldest combo that supports netstandard20) and it still runs fine locally but crashes when deployed.

Edit ... my case probably isn't worth further investigation, I'm doing a custom trigger binding, which is apparently not a supported scenario for Functions.

[katebialiatka]

I can observe the same behavior.
Function was working properly but starting from friday (2018-03-30) we see such kind of error on portal.
Currently, function runs successfully via Visual studio with Microsoft.Azure.WebJobs (3.0.0-beta4) but not on portal.
We use IExtensionConfigProvider for DI. Steps to reproduce are the same as @isaiahwilliams mentioned.

Error message is "Method not found: 'Void Microsoft.Azure.WebJobs.Host.Config.FluentBindingRule1.BindToInput(System.Func2)'.
System.MissingMethodException:"

[codepossible]

Follow the link for announcement below to view the latest version of runtime and SDK currently available in Azure functions. There is a comment on the announcement to get the previous version of Azure Functions Runtime (not recommended).

https://github.com/Azure/app-service-announcements/issues/94#comment-376647094

[codepossible]

I was able to migrate most of the code that I have for my extension to beta5. But still missing a migration path for BindToInput.

[davidebbo]

@codepossible so even with the latest packages, you are still seeing the exact error that started this issue when running on Azure?

[codepossible]

I am able to build the code with latest packages - Built with Microsoft.NET.Sdk.Functions (v.1.0.12) and Microsoft.Azure.WebJobs.SDK (v3.0.0-beta5), but get the following error when trying to run the code locally and on Azure.

Here is the local stacktrace:
System.MissingMethodException: Method not found: 'FluentBinder Microsoft.Azure.WebJobs.Host.Config.FluentBindingRule1.BindToInput(Microsoft.Azure.WebJobs.IConverter2)'.
at WebJobs.Extensions.AzureRedis.AzureRedisConfiguration.Initialize(ExtensionConfigContext context)
at Microsoft.Azure.WebJobs.Host.Executors.JobHostConfigurationExtensions.InvokeExtensionConfigProviders(ExtensionConfigContext context) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\JobHostConfigurationExtensions.cs:line 410
at Microsoft.Azure.WebJobs.Host.Executors.JobHostConfigurationExtensions.CreateStaticServices(JobHostConfiguration config) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\JobHostConfigurationExtensions.cs:line 110
at Microsoft.Azure.WebJobs.JobHost.InitializeServices() in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\JobHost.cs:line 472
at Microsoft.Azure.WebJobs.JobHost.get_Services() in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\JobHost.cs:line 484
at Microsoft.Azure.WebJobs.Script.Utility.CreateMetadataProvider(JobHost host) in C:\azure-webjobs-sdk-script\src\WebJobs.Script\Utility.cs:line 375
at Microsoft.Azure.WebJobs.Script.ScriptHost.LoadCustomExtensions() in C:\azure-webjobs-sdk-script\src\WebJobs.Script\Host\ScriptHost.cs:line 723
at Microsoft.Azure.WebJobs.Script.ScriptHost.Initialize() in C:\azure-webjobs-sdk-script\src\WebJobs.Script\Host\ScriptHost.cs:line 540
at Microsoft.Azure.WebJobs.Script.ScriptHost.Create(IScriptHostEnvironment environment, IScriptEventManager eventManager, ScriptHostConfiguration scriptConfig, ScriptSettingsManager settingsManager, ILoggerFactoryBuilder loggerFactoryBuilder, ProxyClientExecutor proxyClient) in C:\azure-webjobs-sdk-script\src\WebJobs.Script\Host\ScriptHost.cs:line 996

[codepossible]

* Good news to share. *

After @davidebbo reached out to me, I deployed a version of the Extensions on Azure and it worked!

So, the code compiled with beta5 may not run locally but * it works on Azure *.

I am told - the fix for Visual Studio is coming soon.

Until then, my approach has been to downgrade to beta4 and SDK v 1.0.9 to test out the behavior locally and then upgrade to beta5 to deploy. Not the ideal path and I am little hesitant to recommend this approach. But in case you find yourself stuck, it may work for you.

Thank you - @davidebbo for your help.

[CarlosSardo]

Facing the exact same issue here with my dev machine, using VS2017 15.6.2 and Azure Functions and Web Jobs Tools 15.0.40322.0.
When deployed to Azure it works fine!

[codepossible]

Ok people... here is real work around. Thanks to @nzthiago

https://github.com/Azure/Azure-Functions/issues/625#issuecomment-377566084

From the comment, Installing the latest core tool would mean -
npm i -g azure-functions-core-tools@core --unsafe-perm true

[davidebbo]

It took a little longer than we would have wanted, but the updated Azure Functions and WebJobs Tools VS extension is now up. Please go ahead and upgrade. The new version is 15.0.40405.0.

Thanks for your patience on this.

[harjotsmart]

Thanks @davidebbo , It is giving same error after updating azure web job tools as well.
Azure.Functions.Portable.Common: Method not found: 'Void Microsoft.Azure.WebJobs.Host.Config.FluentBindingRule1.BindToInput(System.Func2)'