I'm using the sqlite-net async API to code a Windows Phone app. While writing a unit test to make sure that my adapter to the sqlite-net API created the file properly, I noticed that the adapter continues holding onto the file handle even after it has gone out of scope.
The async connection class (SQLiteAsyncConnection
) does not support IDisposable
so I cannot manually dispose it. Looking at the source, it seems like the async API creates a connection, uses it and disposes it every time. However, when my test cleanup code attempts to delete the created test database, some other resource is still holding onto it.