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

Calls to NativeLibrary should not assume explicit paths #1311

Open
glopesdev opened this issue May 18, 2024 · 0 comments
Open

Calls to NativeLibrary should not assume explicit paths #1311

glopesdev opened this issue May 18, 2024 · 0 comments

Comments

@glopesdev
Copy link
Contributor

It seems extremely error-prone to presume to replace the OS-specific library search strategies. It doesn't feel like library developers should assume they have to rewrite how native libraries are found in the system. Application developers should worry about their specific deployments if this doesn't work for them.

This line:

ok = NativeLibrary.TryLoad(path, out var res);

should really just use the full TryLoad overload.

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

No branches or pull requests

1 participant