|Last Modified:||2013-03-07 21:13:46|
|Version Found In:||1.0.84|
anonymous added on 2013-03-07 10:41:04:
Currently you use "AppDomain.CurrentDomain.BaseDirectory" to determine a base search path for the interop (x86/x64) assemblies, but it would be better if the base is determined by the location of the System.Data.Sqlite.dll itself. This could be done if you replace the existing code with "Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location)". This would allow the assemblies to be moved to a probing path without breaking anything. E.g. if you use an App.config like: <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <probing privatePath="PlugIns" /> <publisherPolicy apply="yes" /> </assemblyBinding> </runtime> For now I use "Environment.SetEnvironmentVariable("PreLoadSQLite_BaseDirectory", Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location));" as a workaround - but I wonder if this could be a better standard behavior. Best regards, Andreas
mistachkin added on 2013-03-07 21:13:23:
The improvements to the native library pre-loading feature that you are asking for have already been implemented on trunk, several days ago, [80f0294664|here].