Cannot bind parameter 'log' to type ILogger.

[forki]

018-12-05T08:11:31.235 [Error] Error indexing method 'StopTransaction.run'
Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexingException : Error indexing method 'StopTransaction.run' ---> System.InvalidOperationException : Cannot bind parameter 'log' to type ILogger. Make sure the parameter Type is supported by the binding. If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).
at async Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexer.IndexMethodAsyncCore(MethodInfo method,IFunctionIndexCollector index,CancellationToken cancellationToken) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Indexers\FunctionIndexer.cs : 272
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexer.IndexMethodAsync(MethodInfo method,IFunctionIndexCollector index,CancellationToken cancellationToken) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Indexers\FunctionIndexer.cs : 167
End of inner exception
at async Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexer.IndexMethodAsync(MethodInfo method,IFunctionIndexCollector index,CancellationToken cancellationToken) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Indexers\FunctionIndexer.cs : 175
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexer.IndexTypeAsync(Type type,IFunctionIndexCollector index,CancellationToken cancellationToken) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Indexers\FunctionIndexer.cs : 103
2018-12-05T08:11:31.260 [Warning] Function 'StopTransaction.run' failed indexing and will be disabled.

Investigative information

Please provide the following:

• Function App version (1.0 or 2.0): 2.0.12210.0
• Function App name: ecartransactions
• Function name(s) (as appropriate): StopTransaction
• Region: West Europe

This is a regression - same function worked before the 2.0.12210.0 upgrade.

open Microsoft.Extensions.Logging
...
[<FunctionName("StopTransaction")>]
let run([<HttpTrigger(AuthorizationLevel.Function, "post", "stoptransaction")>] req:HttpRequestMessage, log:ILogger) = task {
        ...
        use result = new HttpResponseMessage(HttpStatusCode.OK)
        return result
}

[forki]

btw: all my functions have that issue. not a single function is running anymore.

[forki]

which is the last version before that? I can try to manually downgrade

[forki]

Ok downgrading the runtime to 2.0.12180.0 did not seem to fix the problem. Maybe it's yet another instance of the binding redirects issue and I upgraded aspnet deps too far? Microsoft.Extensions.Logging which nuget version is that expected to be?

[forki]

Now that I think about it: yesterday the aspnet 2.2 nupkgs came out and I bet we upgraded that. Will try to downgrade these.

[jpriestley70]

I have the same issue when everything was updated even .Net Core 2.2.
Downgraded .Net Core to 2.0
Downgraded the following Microsoft packages to 2.1

• Microsoft.EntityFrameworkCore
• Microsoft.EntityFrameworkCore.Design
• Microsoft.EntityFrameworkCore.SqlServer
• Microsoft.Extensions.DependencyInjection.Abstractions

This allowed my Startup class with [assembly: WebJobsStartup(typeof(Startup))] to work again and also the ILogger log parameter in my functions.

[forki]

yes reverting to 2.1 did the trick. but this is yet another nightmare. it's hard to maintain

[thinkbeforecoding]

I got it wokring again with the following paket.dependencies :

source https://api.nuget.org/v3/index.json
  framework: netcoreapp2.1, netstandard2
  storage: none
  strategy: min

  nuget FSharp.Core
  nuget FSharp.Data
  nuget Giraffe == 3.1.0
  nuget Microsoft.AspNetCore 2.1.1
  nuget Microsoft.AspNetCore.StaticFiles 2.1.1
  nuget Microsoft.NETCore.Platforms 2.1.1
  nuget Microsoft.NET.Sdk.Functions == 1.0.24
  nuget Thoth.Json.Giraffe  1.1.0
  nuget Thoth.Json.Net 2.4.0
  nuget WindowsAzure.Storage 9.3.2
  nuget NETStandard.Library 2.0.2

[forki]

That looks correct, but boy is it annoying to pin everything. I think azure functions Team needs to reopen the infamous "binding redirects issue" (see #2881) that they proudly closed live on stage.

[forki]

one thing the team might consider to do is in to release a new Microsoft.NET.Sdk.Functions package that pins its dependecies to concrete versions. That way customers would always use these versions

[Hoaas]

Same error occurs if Microsoft.Extensions.Http 2.2.0 is added to the project.

[skotl]

Same for me, having updated to SDK 2.2
I could go back, but don't particularly want to, and I'm not sure I want to be monkeying around with binding extensions.
Is there a solution for ILogger that anyone is aware of?

[forki]

Since dotnet core doesn't even have support for binding redirects, your only option is to downgrade to 2.1 and wait until azure functions upgrades the platform. Am Di., 11. Dez. 2018, 00:13 hat Scott Leckie <notifications@github.com> geschrieben:

…

Same for me, having updated to SDK 2.2 I *could* go back, but don't particularly want to, and I'm not sure I want to be monkeying around with binding extensions. Is there a solution for ILogger that anyone is aware of? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3854 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNA7pZyQnKd1DTeHDs9RGEa3cgShtks5u3uqfgaJpZM4ZCNon> .

[skotl]

Since dotnet core doesn't even have support for binding redirects, your only option is to downgrade to 2.1 and wait until azure functions upgrades the platform. Am Di., 11. Dez. 2018, 00:13 hat Scott Leckie notifications@github.com geschrieben:
…
Same for me, having updated to SDK 2.2 I could go back, but don't particularly want to, and I'm not sure I want to be monkeying around with binding extensions. Is there a solution for ILogger that anyone is aware of? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3854 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AADgNA7pZyQnKd1DTeHDs9RGEa3cgShtks5u3uqfgaJpZM4ZCNon .

Darn - ok, so back to 2.1 for me!
Thanks for the info :)

[jongyllen]

I reverted to the old TraceWriter, it is obsolete but still working.
Also implemented an ILogger that uses the tracewriter so I don't have to rewrite the logging statements in the function.
Will swap it for the dependency injected version when it is fixed

[mikesitch]

We also had to suspend moving to 2.2. Any update on when this will be ready?