Use older version of Microsoft.Extensions.Logging for compatibility #717
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…gets, for compatibility with durable functions host
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using FASTER and Netherite on a Durable Functions host, the it is not possible to load version 6.0.0 of Microsoft.Extensions.Logging.
This appears to be an instance of a well known problem with the functions host not being able to load the latest versions of some dependencies (https://stackoverflow.com/questions/64809716/could-not-load-file-or-assembly-microsoft-extensions-configuration-abstractions).
Since there is no other workaround for this problem at the moment, we are reverting the versions used by the netstandard2.0 and netstandard 2.1 to Microsoft.Extensions.Logging version 3.1.26 which is the newest one that works.