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 found out that all Typemock Assemblys are Registered in GAC.
Except for the Typemock.ArrangeActAssert Assembly.
Is there a reason.
Because this is givin us troubles when making an automated build with TFS.
I think the Typemock.ArrangeActAssert Assembly should be registered in GAC too.
asked by swtrse (4k points)

3 Answers

0 votes

Can you please post more details about the problem you see?
What is the error message?

The reason that typemock.dll is in the gac is technical and is related to the way the Isolator works.
Typemock.ArrangeActAssert.dll is just a standard reference and there is no reason for it to be in the gac. You should make sure that the 'Copy Local' property of its reference is set to true so it will in the same folder of your test assembly.
That been said if you really see no other way you can still install Typemock.ArrangeActAssert.dll in the gac from the command line using the following command:
>> gacutil -i <PathTheIsolatorInstallationFolder>Typemock.ArrangeActAssert.dll
answered by ohad (35.4k points)
0 votes
On my local machine all is working fine. The problem pops up when using an continuous Build environment.

With Typemock.ArrangeActAssert.dll not in GAC the TFS Build give us an Reference not found exception (The type or namespace name 'Isolated' could not be found (are you missing a using directive or an assembly reference?)).
Since Typemock is installed in an different directory on the buildserver that on my local machine this ist totaly logical.
To prevent this problem Copy Local has to be set to false and Typemock.ArrangeActAssert.dll has to be registered in GAC.

I do not see a reason why this should not be the default.
answered by swtrse (4k points)
0 votes
Perhaps you could copy Typemock.ArrangeActAssert.dll to your local 3rd party directory, and reference it from there. That way it will be deployable to the build environment together with the rest of your project files.
answered by igal (5.7k points)