Over two dozen "Typemock Isolator Quickstart" entr

No need - I got it fixed, it was just another one of those things where in the newer version the mocking got a little more accurate in the chained scenario, which is good in 99% of the cases except when one of your developers writes a test that takes advantage of the defect that was fixed.

Our problem was in a couple of tests where Members.ReturnRecursiveFakes used to be returning null but now returns an actual object (or vice versa) - the dev had made one assumption and that changed. Fixed the test by manually specifying what was expected rather than letting it fall to chance.

Thanks, Travis, for letting us know.

Was this an upgrade from version 6.0.8, or an earlier version? I'd like to make extra sure when was this behavior changed.

It was an upgrade from 6.0.8.

It is a little late to report this, but version 6.09 fixes the perpetually expanding menu problem.

Unlike earlier posters, I did not have to run a macro to get rid of the extra items. After uninstalling the old version, all I had to do was bring up VS and click on one of the bogus entries. VS detects they are invalid at this point, and offers to remove them for me. It removes all of them.

Follow that with an install of 6.09, and all is good.

I have this problem from a clean install of Typemock Isolator 2010.

Is there a solution that applies to this version?

Hi,

Which version exactly do you have installed?
You can check that using Typemock -> Configuration.

_________________
Regards

Yonatan Eldar,
TypeMock Support Group

It looks like it is 6.08. I was under the impression that "Isolator 2010" was the 7.x version and replaced the 6.x version.

It would seem then that I need to run the 6.09 hotfix as mentioned above. Is this something I can install over the top of 6.08? If not, please verify that these are the correct steps to resolve the problem:

1. uninstall 6.08
2. execute the macro as presented above
3. install 6.09

Please verify - thank you for your time.

Hi,

Yes, it should work. You can follow the instructions of billster a few posts back on this thread - it should be fine.

Version 6.0.9 and above is OK.

_________________
Regards

Yonatan Eldar,
TypeMock Support Group

Just wanted to provide an alternative solution to running the VS Macro (which didn't seem to work for me). Plus, this solution is much quicker:

1. Close all instances of VisualStudio
2. Uninstall TypeMock
3. Re-open VisualStudio (a reboot was not necessary for me)
4. Go to the VisualStudio Help Menu and click on any of the orphaned TypeMock "help entries"
5. VisualStudio will detect that they are no longer installed and will prompt you whether or not to remove them
6. Click yes
7. Close VisualStudio
8. Re-install any version of TypeMock after v6.0.9 (when this bug was fixed).
9. Re-open VisualStudio and you're good to go :D

There should be 1 TypeMock Help entry and there always will be after subsequent openings of VisualStudio!

HTH

Hi Dave,

Thank you, it seems to be quicker then the macro.