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
Welcome to Typemock Answers. Here you can ask and receive answers from other community members. And if you liked or disliked an answer or thread: react with an up- or downvote Enjoy!
0 votes
Hi,

I have installed Isolator 6.0.3 and tried to run my test case. It fails giving the following error.
System.IO.FileNotFoundException: System.IO.FileNotFoundException: Could not load file or assembly 'TypeMock, Version=5.4.5.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2' or one of its dependencies. The system cannot find the file specified.=== Pre-bind state information ===

LOG: DisplayName = TypeMock, Version=5.4.5.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2
(Fully-specified)
.....
.....
Calling assembly : UnitTestSupport, Version=1.0.0.0, Culture=neutral, PublicKeyToken=86781fa52e072ff9.
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: TypeMock, Version=5.4.5.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2


I was working on version 5.4.5 before moving to latest version. Please let me know how to over come this problem.

Thanks in advance.
asked by (1.9k points)

5 Answers

0 votes
Hi,

First check the GAC at the path: C:\Windows\assembly
make sure you have only one version of Typemock.dll - 6.0.3
Than check that the tests project is referencing the same version.
Rebuild the project and run the tests.

Please let me know the results.
answered by (35.5k points)
0 votes
Still the problem is there for me.
I have checked the GAC and it contains latest version of Typemock.dll.
This seems to be typical issue as couple of other test cases are passing when verified. Problem repeatedly occuring with few test cases for me.
answered by (1.9k points)
0 votes
Hi,

I need a bit more info:
Can you please tell me how do you run your tests? what runner are you using?
Are you using code coverage tool in the tests?
Are you running on 64 bit machine?
answered by (35.5k points)
0 votes
Finally i found the root cause. It's due to one of the dependent assembly was built on TypeMock version 5.4.5 which was causing this trouble. I was using a method of that in my test initialize.

Sorry for troubling you.

Thanks.
answered by (1.9k points)
0 votes
Hi,

No problem, glad it worked :)
answered by (35.5k points)
...