Open tomkluskens opened 6 years ago
@fabiocav FYI - the PR you have open (https://github.com/Azure/azure-functions-host/pull/2734) might help with this.
Functions is not running on ASP.NET core 2.1 right now, but it will be soon and hopefully this error will disappear at that point.
Here's a relevant issue to the upgrade: https://github.com/Azure/azure-webjobs-sdk/issues/1206
Is there a timeline availabe when functions will be running on core 2.1?
No firm timeline at this point, but if you watch the issue @paulbatum linked to, that will be one of the signals of progress in that direction.
Hi, is there any news about when azure functions will be updated to run on dotnetcore 2.1? Or do you have links to info about timelines? At this moment we start migrating our application landscape from 2.0 to 2.1 (as 2.0 reaches End Of Life October 1st 2018) but we can't do that for the azure function parts.
Functions V2 runs on .NET Core 2.1, as of a month or so ago.
Here's the relevant release: https://github.com/Azure/azure-functions-host/releases/tag/v2.0.11888-alpha
Great! We missed that one! We were looking somehow to the wrong repo. Thanks for your quick answer.
I have a function app targetting .net standard 2.0 (using Microsoft.NET.Sdk.Functions 1.0.13).
In the function I want to use a signalr client to send a message to an external signalr hub. I use in the function app the Microsoft.AspNetCore.SignalR.Client (1.0.0-preview2-final) to communicate with the signalr hub.
Running the function app when instantiating a HubConnection, the following exception is thrown in the following method:
Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.ExecuteWithLoggingAsync
StackTrace:
The Microsoft.AspNetCore.SignalR.Client package has dependencies to .net core 2.1 assemblies. Is this causing the issue? And if so, can I work around it with the current version of Microsoft.NET.Sdk.Functions?