I got the same problem. However, finally, I can fix it. Currently, I use Visual Studio 2013 Community Edition. I just use Add->Existing Item... and browse to where the SQLite.Data.SQLite files are in (my case is 'C:\Program Files (x86)\System.Data.SQLite\2013\bin'). Please don't forget to change type of what you will include to Assembly Files (*.dll; *.pdb). Choose 'SQLite.Interop.dll' in that folder. From there and then, I can continue without any problems at all. Good luck to you all. ^_^ P.S. I create web form application. I haven't tried in window form application or others yet.

所以，我的问题是SQLite试图在WPF的设计时加载。由于我只关心x86环境，所以我将CPU首选项设置为x86环境，并将Nuget包中的SQLite.Interop.dll复制到解决方案的根目录。重新启动解决方案，所有问题都消失了。因此，如果遇到设计时问题，请将库放到解决方案的根目录中。

此外，我在运行时遇到了类似的问题，所以我必须将SQLite.Interop.dll的副本放入我的项目中，并将其设置为复制，如果它在属性中较新的。似乎x86和x64提供的文件夹是完全无用的。还需要进一步的调查，但总的来说…在你的项目中手动引用SQLite比使用Nuget包更容易。

此外，官方常见问题解答如下:

(20) When the System.Data.SQLite project is compiled and run from inside Visual Studio, why do I get a DllNotFoundException or a BadImageFormatException (for "sqlite3.dll" or "SQLite.Interop.dll") when trying to run or debug the application? When compiling and running a solution from within Visual Studio that uses the System.Data.SQLite project (including the test project), it is very important to select the correct build configuration and platform. First, managed applications to be debugged inside Visual Studio cannot use the mixed-mode assembly (i.e. because it is always compiled to the platform-specific build output directory). This is necessary to properly support building binaries for multiple platforms using the same source project files. Therefore, only the "DebugNativeOnly" or "ReleaseNativeOnly" build configurations should be selected when running a managed application from inside Visual Studio that relies upon the System.Data.SQLite assembly. These build configurations contain a custom post-build step that copies the required native assembly to the managed output directory (i.e. to enable running the managed binaries in-place). However, this post-build step will only be performed if the selected platform matches that of the operating system (e.g. "Win32" for 32-bit Windows and "x64" for 64-bit Windows). Therefore, it is good practice to double-check the selected build platform against the operating system prior to attempting to run a managed project in the solution.

https://system.data.sqlite.org/index.html/doc/trunk/www/faq.wiki#q20

我的情况有点特殊。我在docker容器中运行一个应用程序，并不断得到以下错误

系统。DllNotFoundException:无法加载共享库'SQLite.Interop.dll'或其依赖项之一为了帮助诊断加载问题，可以考虑设置LD_DEBUG环境变量:libSQLite.Interop.dll:不能打开共享目标文件:没有这样的文件或目录

因此，我设置LD_DEBUG=libs，以找出System.Data.SQLite.dll正在查找的文件夹，以查找SQLite.Interop.dll。

你可以在这里找到关于设置LD_DEBUG的信息:http://www.bnikolic.co.uk/blog/linux-ld-debug.html

一旦我这样做了，我意识到SQLite.Interop.dll被找到了。没有找到的DLL是libSQLite.Interop.dll。我应该阅读整个错误消息。

在谷歌上搜索了几个小时后，我找到了这个关于如何从SQLite源代码编译缺失DLL的指南。

注意，实际丢失的文件是libSQLite.Interop.dll.so

编译源代码时，你会得到libsqlite。interop。so，你需要将它重命名为libsqlite。interop。dll。so，然后将它放到它要找的目录中你可以通过设置LD_DEBUG找到它。

对我来说，System.Data.SQLite.dll查找的目录是/usr/lib/x86_64-linux-gnu/

这对我来说很管用。

With Visual Studio open, search and install SQLite.Core via the NUGET Package manager. Go to Solution Explorer in VS, Right click your PROJECT NAME-->ADD-->NEW FOLDER Name the folder x64 Repeat the process and add folder and name it x86 Right click the x64 folder-->ADD-->EXISTING ITEM Then browse to the DEBUG FOLDER. You will find the x64 folder. Open it and select the "SQLite.Interop.dll" file then hit OK. Repeat step 5 for the x86 folder. Right click the DLL that you just added and select PROPERTIES. In the option Copy to Output Directory, choose Copy always. Repeat step 7 for both DLLs in x64 and x86 folder.

下次构建该项目并使用另一台计算机时，它应该可以正常工作。

我正在做一个简单的控制台应用程序，向SQLite数据库添加一些测试数据，并得到这个错误。项目的配置是“Any CPU”。我通过将SQLite.Interop.dll复制到bin\debug文件夹来修复它。更好的方法是使用@Wil的方法，但是如何为“任何CPU”配置指定该方法呢?

如果您试图在64位项目中运行32位dll，也可能会出现此错误。

当我在x86和x64文件夹中放置相同的文件(32位版本的SQLite.Interop.dll)时，我得到了这个。