Robert Calco wrote:
>
> Dependency Walker is complaining that SQLite.Interop.dll needs but cannot
> find IEShims.dll. This DLL is present on my system twice, in the program
> files directory of both x86 and x64 versions of Internet Explorer,
> respectively.
>
That appears to be a delay-load issue. Those are normally harmless.
>
> I have used NuGet to install SQLite into all three. I'm going to remove it
> from the projects in the WPF and WCF solutions, leaving it only in the
> Shared solution, and resolving all references to the SQLite binaries in
the
> shared solution, for starters.
>
I've never tried to add the same NuGet package to multiple projects in a
single solution before. I'm not sure what happens in that case.
Something that could give us some clues here are the trace diagnostics
emitted
by the native library pre-loading feature. Is it possible for you to modify
your project and add a trace listener prior to using any of the
System.Data.SQLite
classes? If so, you should see output similar to:
Trying to load native SQLite library \"{0}\"...
Failed to load native SQLite library \"{0}\" (getLastError = {1}):
{2}
Also, if your application is part of a web application or is being deployed
to a
location where the "SQLite.Interop.dll" files will not be present in the
appropriate
processor architecture sub-directories, you can use the
"PreLoadSQLite_BaseDirectory"
environment variable to indicate where the native library pre-loading
feature should
look. See the following docs for more information:
http://system.data.sqlite.org/index.html/artifact?ci=trunk&filename=Doc/Extr
a/environment.html
--
Joe Mistachkin
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
