SQLite.Interop.dll locked after running Visual Studio 2012 Unit Test Framework tests

Question

• Visual Studio 2012
• SQLite 1.0.82.0 (from nuget)

I am trying to use the "Run All" command in the "Test Explorer" The following error happens after you run the test once ... after that it will not build anymore, until you restart visual studio

Here is the build error

The Process cannot access the file 'SQLite.Interop.dll' because it is being used by another process

here is the code

using System.Data.SQLite;
using Microsoft.VisualStudio.TestTools.UnitTesting;

namespace Test.Sqlite
{
    [TestClass]
    public class Test_Sqlite_Locking
    {
        [TestMethod]
        public void can_create_table()
        {
            using(var fact = new SQLiteFactory())            
            using (var conn = fact.CreateConnection())
            {
                conn.ConnectionString = "Data Source=:memory:;Version=3;New=True;";
                conn.Open();
                //conn.Close();                
            }

            //SQLiteConnection.ClearAllPools();
            //GC.Collect();
        }
    }
}

I have tried, closing connection, calling ClearAllPools, GC.Collect, and creating the SQLiteConnection directly (instead of the Factory) ... still same issue

This DOES work if you DEBUG ALL TESTS ... but it is when you just Run the tests that this seems to lock it up

Answer 1

I could not find that option in VS2012 (at least not for standard unit tests), therefore I came up with another solution:

The problem you are facing comes from the fact that the unit test runner remains loaded so that repeated test runs are faster. Since SQLite.Interop.dll will probably not change too often, I changed the CopyToOutputDirectory option to PreserveNewest rather than the default Always.

You can do this by opening the properties (F4) view and selecting the SQLite.Interop.dll file in your solution. The only time this will probably still lock up is when you upgrade to a newer version of SQLite and restarting VS2012 then works OK for me.

Answer 2

I worked around this by using the following as a pre-build event on the affected test projects:

for 64-bit:

taskkill /F /IM vstest.executionengine.exe /FI "MEMUSAGE gt 1"

or for 32-bit:

taskkill /F /IM vstest.executionengine.x86.exe /FI "MEMUSAGE gt 1"

This silently kills the execution engine before building the test project. The /FI "MEMUSAGE gt 1" stops the command (and therefore the build) from failing if the execution engine isn't running.

Answer 3

Try this:

• In VS.NET, click on Tools \ Options
• When the dialog appears, click on "Test Tools"
• Click on "Test Execution"
• Uncheck the box "Keep test execution engine running between tests"
• Click OK and restart VS.NET

You should be able run SQLite based tests now without having to restart.

Answer 4

In Visual Studio 2013 - Go to "Test > Test Settings > keep Test Execution Engine Runing" and uncheck it! Works for me.

Answer 5

The workaround provided by Philipp Aumayr (set CopyToOutputDirectory option to PreserveNewest rather than the default Always) works for most scenarios, but not all, unfortunately. As other questions on SO point out, the fact that vstest.executionengine does not terminate is a common issue in VS2012 - worse, Microsoft developers treat this as a feature and by design. The option to prevent this behavior existed in VS2010 but has been removed in VS2012.

If you too have a problem with this "improvement" then please vote on the Microsoft Connect support issue vstest.executionengine.x86.exe (32 bit) - Not Closing (affects both x86 and x64 despite the title).

Answer 6

I know this question is old, but I had this problem and some of the answers here sparked an idea. One of the first problems I encountered when trying to build unit/integration tests around SQLite was that MSTest (which we use for scripted builds) wasn't deploying all of the necessary dependencies to the test run's "Out" directory before running the test, so the tests failed. The best way I found to solve this problem was to add these attributes to my test class:

[TestClass]
**[DeploymentItem("System.Data.SQLite.dll")]
[DeploymentItem("x86\\SQLite.Interop.Dll")]**
public class TestClass

This appears to also solve this issue...I'm guessing this causes VSTest to load a different copy of these dependencies so that VSBuild can still do what it will with the copy in your normal /bin/ directory.

Answer 7

Also make sure that your Database is installed to the correct folder
SQLite Connection Strings

Data adapter that you may want to try as well using SQL Lite Using SQLitew with .NET

SQLiteConnectionStringBuilder builder = new SQLiteConnectionStringBuilder();
builder.FailIfMissing = true;
builder.DataSource = "Insert the fully qualified path to your sqlite db";
SQLiteConnection connection = new SQLiteConnection(builder.ConnectionString);
try
{
  connection.Open();
}
catch(SqlException exp)
{
    // Log what you need from here.
    throw new InvalidOperationException("Whatever exception you want to throw", exp);
}

Read this Article to see if it helps to correct your issue as well System.Data.SQLite.View Ticket

Answer 8

Try disposing of the connection as below. It worked fine for me.

    private void Dispose(bool disposing)
    {
        if (_disposed) return;

        if (disposing)
        {
            if (_dbConnection != null)
            {
                _dbConnection.Cancel();
                _dbConnection.Close();
                _dbConnection.Dispose();
            }
        }

        _disposed = true;
    }