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
I have installed Isolator 7.0 on our build server and updated our build to use the TypemockStart and TypemockStop build activities (we previously used another build activity which uses tmockrunner.exe).

The project I am using has the following (version 6.02) assemblies in it's source control (added via a nuget package):

*Typemock.ArrangeActAssert
*TypeMock.CLI.Common
*TypeMock
*TypeMock.Integration
*Typemock.Interceptors
*TypeMock.MSBuild

When the tests run on the build server they fail with:

Unit Test Adapter threw exception: 
Could not load file or assembly 'Typemock.ArrangeActAssert, Version=6.0.2.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2' or one of its dependencies. The system cannot find the file specified..


All the tests run fine locally using Isolator 7.0 (or 6.0.2).
asked by Squid (3.5k points)

20 Answers

0 votes
Hi,

I just noticed you already sent the file :)
answered by Elisha (12k points)
0 votes
Sorry should have posted that - I noticed the attachment didn't work (too big) so I emailed it through!

Eagerly awaiting feedback :)

From what I see when you have coverage enabled it copies the Assemblies under test into the test folder, but it doesn't copy in the Typemock Dependencies (probably due to the warning in my previous post), from here it fails as it (obviously) can't find them.
answered by Squid (3.5k points)
0 votes
Hi Squid,

What is the exact error you receive? Do you get a message about enable/link error, build/compilation or InvalidOperationException?

In addition, can you tell from the TFS log which .testsettings file is used?
answered by Elisha (12k points)
0 votes
Elisha - no .testsettings specified on build, it searches for a default.

I will email a copy of the TFS build log and MSbuild log.
answered by Squid (3.5k points)
0 votes
Hi jnus,

We haven't been able to create an exact repro of the problem, but we've managed to create a fix that should solve the issue.

A patch with the fix can be found here. Can you please let me know if solves the bug?
answered by Elisha (12k points)
0 votes
Should we apply this patch to our build server (running 7.0.5), even though it seems to be a client package?
answered by jnus (18.9k points)
0 votes
Oops :D you can get the server version here
answered by ohad (35.5k points)
0 votes
Hm - no difference. Same 15 tests are failing. :(
Steps
1: Installed 7.07beta on server -> tests failed
2: Updated projects source control (TypeMock.dll, TypeMock.ArrangeActAssert.dll and Configuration.dll) to 7.0.7 -> tests failed.
answered by jnus (18.9k points)
0 votes
Elisha - The patch you provided me worked brilliantly, thanks so much this is simply awesome!!
answered by Squid (3.5k points)
0 votes
A follow up post. Elisha and I had a remote session and they were finally able to reproduce the error locally. It's a combination of using System.ServiceModel and .NET 3.5 (WCF app). They provided me with a 7.0.7 beta version where the error is fixed.
answered by jnus (18.9k points)
...