Problem with SQLite related nUnit-tests after upgrade to VS2010 and Re#5

Question

After converting to Visual Studio 2010 with ReSharper5 some of my unit tests started failing. More specifically this applies to all unit tests that use NHibernate with SQLite. The problem seem to be related to SQLite somehow. The unit tests that does not involve NHibernate and SQLite are still running fine.

The exception is as follows:

NHibernate.HibernateException : Could not create the driver from NHibernate.Driver.SQLite20Driver, NHibernate, Version=2.1.2.4000, Culture=neutral, PublicKeyToken=aa95f207798dfdb4.
  ----> System.Reflection.TargetInvocationException : Exception has been thrown by the 
        target of an invocation.
  ----> NHibernate.HibernateException : The IDbCommand and IDbConnection implementation 
        in the assembly System.Data.SQLite could not be found. Ensure that the assembly
        System.Data.SQLite is located in the application directory or in the Global 
        Assembly Cache. If the assembly is in the GAC, use <qualifyAssembly/> element 
       in the application configuration file to specify the full name of the assembly.
TearDown : System.NullReferenceException : Object reference not set to an instance of an object.

The exception is the NullReferenceException on TearDown when cleaning up NHibernate objects that wasn't successfully created, but the problem seem to be related to SQLite somehow.

I run my unit tests through ReSharper, but I get the same exception when running them directly through the NUnit.exe application. However, running them through the x86 variant (NUnit-x86.exe) all tests run fine. Can it be related to some mixing of 64bit and 32bit dlls? It still runs fine through VS2008 + ReSharper4.5.

Note that the target framework of my projects still is .NET3.5.

Anyone seen this problem before?

Answer 1

There seems to be a mixup between 64bit and 32bit dlls somehow. Switching to use the x64 variant of SQLite.dll fixes the problem. I'm not sure why VS2008 doesn't give this problem though.

Answer 2

I got the same error, I was sure that it was due to .NET 4.0 and VS 2010, but when I upgraded to Resharper 5 at work (on VS 2008), I got the same error.

I think this is caused by Resharper 5 test runner. When I used TestDriven.NET they all ran successfully.

I hope JetBrains will release a fix soon. According to what I saw on the forums, they are aware of the problem, so it should not take too long to have a fix.

While this is fixed, I will use TestDriven.NET to run my tests. But I will miss the great Resharper UI ;)