System.Data.SQLite

Login
This project makes use of Eagle, provided by Mistachkin Systems.
Eagle: Secure Software Automation
Ticket Hash: 449885cc5730f277dfe5449d2d9287023b3338a7
Title: Opening connection fails when data source path contains # character
Status: Closed Type: Incident
Severity: Important Priority: Medium
Subsystem: Integration_Via_PInvoke Resolution: Unable_To_Reproduce
Last Modified: 2015-06-26 03:11:29
Version Found In: 1.0.97
User Comments:
anonymous added on 2015-06-12 23:24:48: (text/x-fossil-plain)
Trying to make a connection to SQLite database from the following path failed:
C:\Prjects\C#\Test_Prj

I just renamed C# to CSharp and tried again and it started working.

The error message I was receiving was:
Unable to load DLL 'SQLite.Interop.dll': The specified module could not be found.

mistachkin added on 2015-06-13 21:42:17: (text/x-fossil-plain)
Can you please provide the exact connection string you used?  Also, did the
directory provided in the connection string (e.g. "C#") actually exist?

anonymous added on 2015-06-14 11:02:48: (text/x-fossil-plain)
Hi,

The connection string is as follows:
<add name="DataContext" providerName="System.Data.SQLite" connectionString="Data Source=|DataDirectory|db.sqlite3; Version=3;" />

The mentioned directory (C:\Prjects\C#\Test_Prj) and the database file both exsit.

I'm using .net 4.5.2, MVC 5.2.3 and Entity Framework 6.0.0.


Please let me know in case you need any more details. :)

mistachkin added on 2015-06-15 20:31:57: (text/x-fossil-plain)
I'm still unable to reproduce this.  Perhaps it requires using the Entity Framework?

Also, it sounds like an issue with the NuGet package.  Which ones, if any,
are you using?

Is the machine 32-bit or 64-bit?

anonymous added on 2015-06-17 16:54:17: (text/x-fossil-plain)
Hi,

I have added SQLite to my project via NuGet package and I'm using Entity Framework 6.0.0 on a 64bit machine. :)

Thanks for looking into it.

mistachkin added on 2015-06-17 18:36:12: (text/x-fossil-plain)
I'm unable to reproduce this issue, even with EF6.  Perhaps some other component
is interpreting the "#" improperly?