chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes
Hi,
This is a strange issue.
It seems as though the SQLConnection isn't registered correctly. :evil:
It could be because you are running in different threads.

In order to solve this could you please
1. post the code where you use the SQLConnection.
2. tell me what is done on the different threads and when are the threads setup
3. try setting up the Mocks before creating the new DatabaseOrderHandler
4. try using MockAll.
asked by scott (32k points)

4 Answers

0 votes
Thanks,
This will help us try to solve the issue.
answered by scott (32k points)
0 votes
Hi,

This is still under investigation. We've found that the CLR is making calls using the SQL-types, which affects the expectation recording and therefore their verification. This is obviously new with 3.5 framework.

We'll let you know as soon as we have a solution.
answered by gilz (14.5k points)
0 votes
Hi,

Sorry but there are no news on this yet. :(
This is a tough one and we are still trying to figure out the exact problem.
answered by lior (13.2k points)
0 votes
Hi,

Just to let everyone know, we have included the fix for this on the 4.2.2 release.
answered by lior (13.2k points)
...