Azure-functions-host: .net core 2.2

[fileman]

Is there any plan/roadmap for .net core 2.2 (preview) support?

[paulbatum]

My rough plan is as follows:

1. We'll prepare branches that target .NET Core 2.2 preview within the next month (so by mid-November)
2. We'll release an update of Functions V2 that runs on 2.2 within ~6 weeks of the .NET Core 2.2 RTM

cc @fabiocav in case he sees any issues with this plan.

We won't be doing any official releases for builds that target the 2.2 previews (once the branches exist you can of course grab them and build them yourself).

I'm going to leave this issue open to track the work.

[espray]

@paulbatum any update/timeline on this?

[paulbatum]

This slipped a little. I think step 1 is partially done already, @fabiocav has a branch somewhere, but its not ready to go yet. I expect this to be done by the end of Jan.

[jsheetzati]

It is unfortunate that Azure Functions lags behind the rest of the ecosystem and is preventing us from upgrading to .NET Core / ASP.NET Core 2.2. Any particular reason this project doesn't follow the normal release schedule for .NET Core?

[paulbatum]

If you mean hold up .NET core releases such that they only happen when Azure Functions is ready, I think the .NET Core team and community would push back on adding additional gates that slow down .NET Core.

If you mean making sure that Azure Functions itself is able to do same-day releases as .NET Core without acting as a release gate on .NET Core itself, then I think this is mostly about the constrained developer resources on our team. Generally we will prioritize customer investigations and bug fixes over this type of work and so if we don't have the bandwidth, it slips. For future .NET Core releases we will try to start the update process earlier (during preview) to help mitigate this. I think this particular case was made worse by the fact that .NET Core 2.2 dropped pretty close to the holidays, extending the lag period longer than we aim for.