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!
+1 vote

When running nunit2.x tests with TypemockIsolatorServer-8.6.2.0.324762729, we get an exception saying that  Typemock.Interceptors.dll version 8.6.2 cannot be found... I checked and it is not being installed in the GAC in this server (our other 2 servers are fine; dll shows up in GAC).

Exception Info: System.IO.FileNotFoundException


Why would the dll not register in the GAC?

asked by (1.6k points)

1 Answer

0 votes

Hello Alejandro,

How do you run your tests on the build server?

I recommend following the server installation instructions that are written in our documentation, and using auto-deploy.  

Try running: 

TMockRunner.exe -deploy \"C:\\Program Files (x86)\\Typemock\\\\Isolator\\8.6\\BuildScripts\\AutoDeploy\" ... [rest of the script]

Please let me know if it helps.

Cheers,

Sapir

answered by (3.1k points)

Hi,

 We are issuing this PowerShell command in order to generate code coverage with dotCover:

 $TYPEMOCK_RUNNER $dotCoverFullPathExe analyze $CCConfigurationFileFullPath /Output=\"$CCRelativeOutputPath\" /TempDir=\"$CCRelativeTempPath\" /TargetWorkingDir=\"$ CCRelativeTargetWorkingDir\" /TargetExecutable=\"$CCNUnitExeFullPath\"

 Thank you for suggesting Auto-Deploy: We will consider this option if we cannot get the server-installer to work properly.

https://www.typemock.com/docs/?book=Isolator&page=Documentation%2FHtmlDocs%2Fautodeploy.htm

 

Is there something wrong with the TypeMockIsolatorServer  installer?

Hi Alejandro, 

There is nothing wrong with the server installer. There are two ways to install Typemock on the server: manually or automatically (auto-deploy).

In both ways the -deploy command is needed.

So in your case, I would recommend you to use the following command:

$TYPEMOCK_RUNNER  -deploy \"C:\\Program Files\\(x86)\\Typemock\\Isolator\\8.6\\BuildScripts\\AutoDeploy $dotCoverFullPathExe analyze $CCConfigurationFileFullPath /Output=\\\\\\\"$CCRelativeOutputPath\\\\\\\" /TempDir=\\\\\\\"$CCRelativeTempPath\\\\\\\" /TargetWorkingDir=\\\\\\\"$ CCRelativeTargetWorkingDir\\\\\\\" /TargetExecutable=\\\\\\\"$CCNUnitExeFullPath\\\\\\\"

Please keep me updated.

Cheers,

Sapir.

...