Use path for loading native dependencies #10347
Merged
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.
So we still have some issues loading native dll's in scenarios where the Coreclr does not raise a ResolvingUnmanagedDll event notification.
So ... what we do with this PR, is for any native dll that msbuild identifies as should be copied to the output directory, we add the directory containing that dll to the Path environment variable for the process. This should increase the range of scenarios where native .dll loading currently fails.
I also have made the code netstandard2.0, since fcs is currently netstandard2.0 only.
/cc @jonsequitur --- this should fix the sqllite notebook issue.