.NET Core - Improve auto loading of NLog extension dlls #2431
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.
NetCore-Console-Applications will usual be compiled to a dll, that is run by the dotnet-tool.
The NLog-package-reference will be loaded from an isolated path, and using this path to load NLog-extension-dlls will result in empty result.
Added extra fallback locations when the NLog-assembly-path returns empty file-list:
But it will not help with dlls coming from Nuget-packages. So maybe it is better to implement something using
DependencyContext
api to resolve the DLLs and their locations that are part of the application's dependency graph.