Re: [sqlite] [System.Data.SQLite] Using sqlite3.dll instead of Interop.dll - what's the trade-off?

2016-10-20 Thread John Reynolds
A follow-up on this (and a late thanks!): I've used your answer to write some build instructions for Ubuntu and Raspbian at http://blog.wezeku.com/2016/10/09/using-system-data-sqlite-under-linux-and-mono/ I've also modified the F# SQLProvider type provider so that it no longer always loads

Re: [sqlite] [System.Data.SQLite] Using sqlite3.dll instead of Interop.dll - what's the trade-off?

2016-09-16 Thread Joe Mistachkin
John Reynolds wrote: > > My question is: what are the trade-offs of not using > SQLite.Interop.dll? > There are various compile-options and extensions baked into the "SQLite.Interop.dll" that are not enabled and/or included by default with "sqlite3.dll". One that is somewhat important, is the

[sqlite] [System.Data.SQLite] Using sqlite3.dll instead of Interop.dll - what's the trade-off?

2016-09-16 Thread John Reynolds
Hi, (Sorry if this becomes a double post - I first tried posting from Nabble) I've compiled System.Data.SQLite.dll with the "/property:UseSqliteStandard=true" option, so that it will load sqlite3.dll (or it's Linux equivalent) instead of SQLite.Interop.dll. The advantage of this is that you can