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
Ask a question
The Unit Testing Company
Development Resources
Knowledge Base
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.

Related questions

Strange Build Problem

0 votes
Hi,

I'm referencing the .NET Framework 2.0 version TypeMock.dll in my test project, which is version 4.02. I can build and test my unit tests locally and everything is fine.

We I go to build the application on a remote server, the reference is changed to TypeMock.exe instead of TypeMock.dll. :( Thus all my test projects fail because they can't find the right assembly. I have installed 4.02 on the remote machine and I'm using Team Build to build the solution.

Any suggestions on how to fix this problem?

Thanks,
Eric
asked by eschatzy
Report User
 (3.8k points)

2 Answers

0 votes
Hi Eric
Please check if if the 'Copy local' property of TypeMock.dll is set to true
If it is change it false. (To check it: Right click on TypeMock.dll in
the solution explorer and choose Properties)

If you have the enterprise license you can use the
auto deploy feature which is designed for running TypeMock
on build servers.

Please tell me if it helps.
answered by ohad
Report User
 (35.4k points)
0 votes
Eric hi,

Just wanted to let you know that in the 4.1.0 release we have renamed the TypeMock.exe so this kind of confusion on the compiler side should not happen anymore.
answered by lior
Report User
 (13.2k points)
...

Products

Help

Company

Community

Contact

Typemock Store (US toll FREE 866–895–4680). Copyright © 2006 Typemock Inc. All rights reserved. Terms of Use.