Check AppContext.BaseDirectory for powersync.dll#28
Merged
Conversation
Chriztiaan
approved these changes
Jan 5, 2026
Collaborator
Chriztiaan
left a comment
Chriztiaan
left a comment
There was a problem hiding this comment.
Looks good, thanks for looking into this!
Chriztiaan
previously approved these changes
Jan 5, 2026
Chriztiaan
approved these changes
Jan 7, 2026
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
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.
Fixes #14 by checking the application's base directory for the PowerSync SQLite3 extension library.
Currently,
PowerSync.Commononly checks the "portable deployment" path (<approot>/runtimes/<rid>/native/powersync.{dylib,so,dll}) for the extension. However, there a number of technologies (Windows Application Packaging projects, .NET Framework 4.8, etc.) which don't follow this convention and instead place all shared libraries in the same directory as the executable. This PR adds a check to see if it can findpowersync.{dylib,so,dll}in the root folder, and if so, loads that library instead of searching for theruntimes/<rid>/nativeone.I considered allowing the user to configure the path to check for
powersync.dll, but decided against it since practically all .NET apps use either the flattened deployment or the structuredruntimes/<rid>/nativedeployment already.