Update Microsoft.Extensions.DependencyModel to v3

[skomis-mm]

• fixes #197 to some extent for netstandard2.0 target: the new package uses System.Text.Json instead of Newtonsoft.Json to parse .deps.json files.
• no need to use workaround from #218 since the new package doesn't bring .NET Core 1.x transitive dependencies, as 2.0.4 of Microsoft.Extensions.DependencyModel does.

[nblumhardt]

👍

[Ted-chiptech]

Start to have this error message in Azure Function V3:

Could not load file or assembly 'Microsoft.Extensions.DependencyModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.

[nblumhardt]

Hi @Ted-chiptech - thanks for the heads-up. Can you please let us know which versions you're dealing with (packages, TFMs and runtime), along with a stack trace, in a new issue? May be a regression, but we'll need more info to pin it down. Thanks!

[Ted-chiptech]

Hi @Ted-chiptech - thanks for the heads-up. Can you please let us know which versions you're dealing with (packages, TFMs and runtime), along with a stack trace, in a new issue? May be a regression, but we'll need more info to pin it down. Thanks!

Hi @nblumhardt, I was using Serilog.Settings.Configuration V3.2.0, The Azure Function runtime is V3, TargetFramework is netcoreapp3.1. then I will get the error above. (The error will show up immediately when starting the project)

However, if I roll back the Serilog.Settings.Configuration package to V3.1.0, everything works fine. Since the error is about 'Microsoft.Extensions.DependencyModel', I think it probably has something to do with this PR. Thanks!

[skomis-mm]

Just checked, the Azure Functions host tied to v2.1.0 of Microsoft.Extensions.DependencyModel and the new version of Serilog.Settings.Configuration brings 3.0.0 to the function's *.deps.json which affects the host. 😕

Not sure yet what is the best way to handle this other than to revert this change..

[nblumhardt]

Nasty... Since Azure Functions will no doubt be updated someday, another option is to continue supporting it via 3.1.0, for now ....

[skomis-mm]

@Ted-chiptech , @nblumhardt the source issue.
To summarize, there are a couple of options:

1. downgrade Microsoft.NET.Sdk.Functions to version 3.0.3 or
2. add undocument build property to .csproj

<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>

3. see if you can migrate to out-of-process executable

[thyde1]

@Ted-chiptech , @nblumhardt the source issue.
To summarize, there are a couple of options:

1. downgrade Microsoft.NET.Sdk.Functions to version 3.0.3 or
2. add undocument build property to .csproj

<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>

1. see if you can migrate to out-of-process executable

Alternatively you could include

<ItemGroup>
    <FunctionsPreservedDependencies Include="Microsoft.Extensions.DependencyModel.dll" />
</ItemGroup>

in your functions .csproj to preserve only this dependency, and not all, as using _FunctionsSkipCleanOutput would achieve.