Dependencies to Microsoft.Extensions.* version >= 2.1

[codecontemplator]

Hi,

This is more of a question than a bug report. We note that the latest Azure Web Jobs SDK takes dependencies on the following Microsoft.Extensions packages:

• Microsoft.Extensions.Configuration (>= 2.1.0)
• Microsoft.Extensions.Configuration.Abstractions (>= 2.1.0)
• Microsoft.Extensions.Configuration.EnvironmentVariables (>= 2.1.0)
• Microsoft.Extensions.Configuration.Json (>= 2.1.0)
• Microsoft.Extensions.Hosting (>= 2.1.0)
• Microsoft.Extensions.Logging (>= 2.1.0)
• Microsoft.Extensions.Logging.Abstractions (>= 2.1.0)
• Microsoft.Extensions.Logging.Configuration (>= 2.1.0)

These packages have been updated to a new major version (3.1.9 is the latest release and version 5.0 is coming).

When, for example, we use the latest Entity Framework, version 3.1.9 that has a dependency on
Microsoft.Extensions.Logging (>= 3.1.9) it seems like we have a potential problem with a transient dependency conflict.

In practice it seems to work, as long as we make sure that Microsoft.Extensions.Logging (>= 3.1.9) is selected but we are worried that we might bump into runtime issues.

What is your take on this? Is the Microsoft.Extensions.* backwards compatible from 3.x (and soon 5.x) to 2.x? If not, are there any plans to upgrade to newer dependencies any time soon?

Thanks for your attention and thanks for providing the Azure Webjobs SDK.

[ThejaChoudary]

@codecontemplator The dependencies of.net core and dependencies of DOT Net standard are different things, so there should not be any conflict.Please let us know if the conflicts occurs so that we can investigate further.

[codecontemplator]

Thanks for the response @ThejaChoudary . Please have a look at https://github.com/collector-bank/azure-webjobs-sdk-issue-2618 for a repro case of a the problem we are experiencing.

[v-anvari]

Hi @codecontemplator , I have tried the repro that you have provide. I am able to repro the issue and get the "System.MethodAccessException". Triaging this issue in order to perform detailed analysis.
I am not sure if it is a dependency issue, because I tried different workarounds by adding required package reference and update few packages, but yet it did not work. This seems to be more of an EF core issue.

cc: @brettsam /@fabiocav , tagging them for more context