Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silk.NET.Core.Loader.DefaultPathResolver does not check the directory of its own assembly #2128

Open
slxdy opened this issue Apr 17, 2024 · 1 comment

Comments

@slxdy
Copy link

slxdy commented Apr 17, 2024

The DefaultPathResolver normally assumes that the library is either located in the domain's base dir or the main module's dir (which should usually be the same anyway), but this becomes a problem when Silk is loaded from a different directory. One solution would be to just set the current directory to Silk's directory... or at least that would've been the case if the resolver checked the current directory.

I believe the DefaultPathResolver should also check the directory of its own assembly. Otherwise, it should at the very least check the current directory. This will allow developers to place Silk in directories separate from the exe.

@slxdy
Copy link
Author

slxdy commented Apr 17, 2024

For context, I am using Silk in a plugin for another application, and since the plugin has its own directory, Silk cannot find its native libraries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant