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 just installed the beta to check out the new debugger integration. However, I cannot see any painting of methods when debugging. Worse, however, is the fact that single stepping through a recording block still leads to very weird behavior.

Do I need to enable something to get this to work? I have looked through the Configuration and I can't find anything. Also, I have upgraded my reference and built everything from scratch to no avail :(

I have tried this in both VS 2005 TS and VS 2008 TS.

asked by brian.rasmussen (7.2k points)

3 Answers

0 votes
Hi Brian,

It seems like you're experiencing an installation issue. This might be the result of the addin DLL being locked at the time of the installations. So in order to make sure you are working with the correct version, here's what
I'd like to try:

1. Shut down any instance of VS and uninstall the 4.2.1 version.

2. Go to (the equivalent location)
C:Documents and SettingsAll UsersApplication Data Microsoft visualstudio 9.0 Addins (for the VS2008 version)

C:Documents and SettingsAll UsersApplication Data Microsoft visualstudio 8.0 Addins (for the VS2005 version)

3. Delete the files:
a. TypeMock.AddIn2007.dll and TypeMock.AddIn2007.AddIn files for VS2008
b. TypeMock.AddIn2005.dll and TypeMock.AddIn2005.AddIn files for VS2005

4. Re-install Typemock Isolator.

After that, re-try running your tests. Let me know how this works out.
answered by gilz (14.5k points)
0 votes
Sorry about the silence. Other tasks ate all my time :(

Actually I couldn't get it to work even after a complete uninstall followed by a reinstall. However, I have moved to another PC in the meantime and now I cannot reproduce the problem so unless it reappears consider it solved.

answered by brian.rasmussen (7.2k points)
0 votes

As I said this is probably an installation issue. Let me know if this comes up again on the new computer.
answered by gilz (14.5k points)