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 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.
0 votes
Can anyone provide some advice on how to run TypeMock in concurrent builds. We are seeing sporadic failures that I suspect come from multiple concurrent builds registering/unregistering typemock using the NAnt task.

For example:
Project 1 Register |--------------| Unregister

Project 2 --------- Register |----x failure

Looking at the NAnt output, register succeeds, but unregister fails with the following message:
[echo] Stopping TypeMock...
[typemockstop] Error undeploying TypeMock.NET TypeMock.NET was not deployed using Auto Deploy
[echo] TypeMock stopped.

Also, the failing tests had the following message:
[exec] *** You are running a 64 bit application with TypeMock.NET 32 bit.
[exec] Please install TypeMock.NET x64.
[exec] Note: .NET 2.0 applications will by default run on 64 bit
[exec] at TypeMock.MockManager.Init(Boolean collectAllCalls)
[exec] at TypeMock.MockManager.Init()

Any help would be appreciated.

- Michael
asked by adoptableCoho (1.2k points)

4 Answers

0 votes
Hi,
Please tell me if you are linking TypeMock or just deploying.
answered by scott (32k points)
0 votes
Here are the two lines we use to register & start:
<typemockregister company="${typemock.company}" license="${typemock.license}" autodeploy="true" />
<typemockstart />

And here is unregister:
<typemockstop undeploy="true" />

Is that what you were looking for?

- Michael
answered by adoptableCoho (1.2k points)
0 votes
Having thought about it a moment...

Not linking, just deploying.

- Michael
answered by adoptableCoho (1.2k points)
0 votes
:arrow: Remove the undeploy, don't unregister
You are undeploying/uninstalling TypeMock so it will effect other tests 8)

use: <typemockstop/>
answered by scott (32k points)
...