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
Hello.

This problem is difficult to reproduce.

In VS 2012 sometimes typemock locks our libraries.

More detailed description looks like this:
1. We run VS and compile solution (successfully)
2. Change a library
3. Run compilation again
4. Very often step 3 doesn't produce any issues
5. We repeat step 2-3 a lot
6. We get compilation error that "X library is used by another process"
7. We disable typemock, restart VS
8. We never see this error again

So right now before writing new unit tests we should activate Typemock and restart VS. (and then disable it)

It's very annoying.

Any ideas ?
asked by IluhaRus (640 points)

4 Answers

0 votes
Hi,
Sorry for the delayed answer.
Not sure I understand step 2. What do you mean by "change a library"?
Also, which version of Isolator are you using?
answered by ohad (35.4k points)
0 votes
Hi,
by step 2) I meant that we change code in some project and try to compile that project

We use 7.5.0.19
answered by IluhaRus (640 points)
0 votes
Hi,
Thanks for the info.
Can you please contact our support via mail?
Our support mail is: support at typemock.com
We would like to continue investigate the issue offline.
answered by ohad (35.4k points)
0 votes
We fixed this issue.
I've attached a link to our new version.
Let us know if it solved the problem.
answered by Bar (3.3k points)
reshown by alex
...