System.Data.SQLite | from system.data.sqlite.org | Database library

there might be a problem on opening and closing the connection 2 times: Could you try it like this:

I've run into the same issue. In my experimentation, I found that changing the double backslash into a triple backslash worked. Obviously, there's a significant bug in the System.Data.SQLite library.

According to SQLite docs:

In-Memory database ceases to exist as soon as the database connection is closed. Every :memory: database is distinct from every other. So, opening two database connections each with the filename ":memory:" will create two independent in-memory databases.

By default each time session is opened - new connection is created. So this error is expected behavior with default settings.

But you use some custom connection provider SQLiteInMemoryConnectionProvider that reuses once opened connection. So I would say the problem is inside SQLiteInMemoryConnectionProvider - it's not ready for async code.

Make sure that your connection provider implements both GetConnection and GetConnectionAsync methods. Something like:

First of all, if your application relies on the working directory ("Start in") to be set to the same folder as the .exe then it is broken. The working directory can be anything if the user invokes your application with "Open with" or from a terminal. Don't read/load anything relative to .\ in your application other than filenames passed as command line parameters.

Why does your shortcuts working directory end with \x86? Because you asked it to!

From the CreateShortcut documentation:

$OUTDIR is stored as the shortcut's working directory property. You can change it by using SetOutPath before creating the shortcut or use /NoWorkingDir if you don't need to set the working directory property.

From your example $OUTDIR is set by SetOutPath "c:\test22\x86\". To set a specific directory for the shortcut, use SetOutPath before CreateShortcut.

I recently had a similar problem when I upgraded from 1.0.113 to 1.0.115. It appears that the dependent native binaries are not correctly copied any more.

Adding these two lines to the post build step of a project (doesn't really matter which one in your solution) helped:

Installing Sqlite with ado.net on a WPF .NET Framework project, is relatively easy if you know the steps. Thanks to MagicAndre for providing guidance. Here we go:

1 - Install the toolbox from here. This is straight forward.

2 - Install GAC from here. Now here is where I was failing. I was installing the 64-bit package only, while the 32 is needed for the GAC. So download and install:

• sqlite-netFx46-setup-bundle-x86-2015-1.0.115.0.exe
• sqlite-netFx46-setup-bundle-x64-2015-1.0.115.0.exe
  
  When installing the 32-bit package, be careful to check as per below image:
  
  
  
  

3 - If you haven’t created your db, download DB Browser from here. Create your db, place a copy within your project, and include it. You can set the build action to content if you are going to distribute the app later.

4 - Create a solution in visual studio, and nugget install: System.Data.SQLite: This will auto install the other 4 packages as well as EntityFramework

5 - In visual studio, go to your server explorer, right click Data connections, add connection

Change your data source to: SQLite Provider (Simple for EF6 by ErikEJ) (SQLite Provider (Simple for EF6 by ErikEJ))

A new window will open The connectionString line at the top would be in this format:
Data source="C:\Users...\Documents\Visual Studio 2019\Projects\sqlite\sqlite\demo.db";Version=3;
Data source=path;Version=3;



Click ok and the connection will appear in server explorer.

6 - ADO.NET:
Right click solution, add, add new item. Go to Data and select ado.net EF Designer from database (database first) and your connection should appear:



Click next, select all tables required, and click finish. Your edmx file will then be prepared and opened.

7 - Within your app.config entityFramework section, the following lines should be there:

ExecuteScalar returns null when zero rows are returned from a query; it returns DBNull.Value when at least one row is returned and the value in the first column is a database null.

So: your query is not returning rows. Check whether that is expected, and if not: fix it. I would, however, be much more concerned about the SQL injection vulnerability in AND name='"+ tableName +"'";; parameters should always be preferred.

You can try this SaveHistory() method

It turns out that SQLite is unable to handle migrations anyway, so it is not a viable option.