This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I currently migrated an application from VS 2008 + Lightspeed 3.1 to VS 2010 + Lightspeed 4. Having made no code changes at all, the application throws a "System.DllNotFoundException" as soon as it tries to access an SQLite database. According to the exception the DLL "SQLite.Interop.dll" can not be found. But this file does exist in the directory of the executable (and the System.Data.SQLite.dll). Searching the web for a solution I found a thread stating that the SQLite assemblies need to be built targeting the same .NET framework as the application using them: http://www.mail-archive.com/sqlite-users@sqlite.org/msg61652.html In another post someone mentioned that the target platform for the application (x86 / x64) should also match. I use Windows 7 64bit. The application is built for x86. The target framework is 3.5. The application runs fine on my machine where .NET 3.5 and .NET 4 are installed, but not on a test machine that only has .NET 3.5. Can you reproduce this error? What else could I try? |
|
|
|
|
We have updated the SQLite provider to 1.0.74 with the next nightly build so you should try this and see if this helps resolve the issue. We noticed that SQLite has switched back to a unified mixed mode assembly so we are now including that rather than the seperate interop assembly. Let us know if you continue to have any issues. We are compiling against the 32 bit 3.5 assembly but if you are building a 64 bit application and need to use the 64 bit assembly then you can just download and install the 64 bit mixed mode assembly (Setups for 64-bit Windows (.NET Framework 3.5 SP1 from http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki) and reference that assembly instead of using the one we provide. If you are targetting the 4.0 framework you can swap in either the 32 bit/64 bit versions as per above, or if you are targetting 32 bit on 4.0 you can use the existing assembly by adding the following to your app.config <startup useLegacyV2RuntimeActivationPolicy="true"/>
Jeremy |
|
|
|
