SQLite provider ResolutionPath fail about sqlprovider HOT 8 CLOSED

Thanks for reporting this. The only change related to this is the commit f48f7dd to support ; in resolution path so that you can feed multiple resolution paths. It shouldn't change the single-path-case at all, but apparently it has.

I don't totally follow the workaround. Where is your SQLitePCLRaw.core ?

from sqlprovider.

If I place the SQLitePCLRaw.core and the other dlls in the same folder as the project file and source file it works. If I move them to the ResolutionPath folder it does not work. Is there a default resolution path where the provider looks for the files?

from sqlprovider.

The default resolution path should be what you defined, however a few things to consider:

Is this script (fsx) or a project (fs)?

For projects, the resolution path should be used in design-time/compile-time only and runtime the files should be copied to the bin-folder (e.g. by adding them as reference files or any other way) because it doesn't make sense to look resolution path from compiled code.

For scripts it doesn't matter so much, but I guess more the question is, have you given a relative path like "./mylibs" or an absolute path like __SOURCE_DIRECTORY__ + "/mylibs", because the scripts are sometimes executed in weird temp project paths.

from sqlprovider.

I am using a project, and the error is raised at compile-time. I have also tried to exchange the path with __SOURCE_DIRECTORY__ + "/libs/win-x64" but no success

from sqlprovider.

Would you have a sample repo, I could try with my Mac at some point?
The database file name is in the connection string. Do you have full path there or no?

Edit: sorry, just noticed this is Windows 11. But I'm still unable to reproduce this, your code works perfectly.

from sqlprovider.

Hi @Thorium. Sorry it took a while to respond, I got very busy at work with other stuff.
I created a repo here that you should be able to use to reproduce the issue.

from sqlprovider.

Thanks for the sample repo.
Issue fixed in 1.3.36

from sqlprovider.

Great! Thanks!

from sqlprovider.