praeclarum / praeclarum/sqlite-net
sqlite3.dll remains locked after running the tests
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
After I run all the tests in the SQLite.csproj project there remains a lock on sqlite3.dll file preventing me from rebuilding or rerunning the tests until I restart Visual Studio. Curiously enough, I don't encounter this problem running the same tests from SQLiteMetroTests.csproj. This is the error I get:
Unable to copy file "C:\Users\Damir\Documents\GitHub\sqlite-net\lib\x86\sqlite3.dll" to "bin\Debug\sqlite3.dll". The process cannot access the file 'bin\Debug\sqlite3.dll' because it is being used by another process.
I'm using Visual Studio 2012 RC built-in test runner with NUnit Test Adapter (Beta 2) v0.92. Is anyone else encountering this issue? Could it be a bug in Visual Studio or the adapter?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the tests in SQLite.csproj with the Visual Studio 2012 built-in test runner and observe the lock on bin\Debug\sqlite3.dll. Compare the behavior with SQLiteMetroTests.csproj and investigate the NUnit Test Adapter interaction. Done means the DLL is released after testing so the project can rebuild and rerun without restarting Visual Studio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sqlite
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100