Tests don't run with Visual Studio 2012 installed.

Hi Paul,

Just to be sure: Isolator 6.2.2 dosen't run on VS 2012.
If you're running tests that you created on VS 2010, but on VS 2012, you'll need to upgrade your version to 7.0.9. You can download it from https://www.typemock.com.

If it's not the case, Please let us know.

Thanks for your reply, NofarC.

I'm not trying to run the tests in VS 2012. I have both VS 2010 and VS 2012 installed, but am only trying to run the tests in VS 2010, and they are failing as I've described above.

I also had this problem a couple of months ago when I installed the VS 2012 release candidate. The only way I could fix it was to uninstall VS 2012 RC, uninstall VS 2010 (and SP1) and reinstall VS 2010 (and SP1). I was hoping I wouldn't see the issue again once VS 2012 was released, but alas, here I am.

Any ideas?
Thanks,
Paul

Hi Paul,

Do you run Nunit with Isolator?

Hi Alex,

Yes, we are using NUnit 2.5.10. Sorry, I should have mentioned this in my question.

Thanks,
Paul

First things first, the issue is real.

Installing VS2012 installs .NET 4.5 and .NET 4.5 runs on the 4.0 CLR, which is the same as .NET 4.0 is using. However, installing .NET 4.5 does seem to modify the the 4.0 CLR. You can see this in the version number: v4.0.30319.269 before .NET 4.5 is installed and v4.0.30319.17929 after .NET 4.5 is installed.

This "new" CLR seems to "freak out" some older versions of TypeMock that should support the .NET 4.0 CLR. I have found that TypeMock 6.0.10 stops working when VS2012 is installed, but that upgrading to TypeMock 6.2.5 fixes it. It could be that TypeMock 6.2.2 has the same issue and making the jump to 6.2.5 would fix the issue for you as well.

Download for TypeMock 6.2.5: https://www.typemock.com/files/TypemockI ... e6.2.5.msi

Thanks for the suggestion halstein.

Unfortunately, upgrading to 6.2.5 did not make the problem go away. On a whim I tried upgrading to the free trial of 7, and this DID get me past this problem, (though there are lots of errors because I'm not referencing the correct TypeMock DLL).

I'm glad to have found this, but saddened. We are not yet prepared to upgrade to 7 (and update all of the branches of our product to use 7), but we also can't seem to have both VS2010 and VS2012 on our machine at the same time with 6.2.x.

It is time for me to do real work - not just experimenting with VS2012, so I now have to uninstall VS2010 and VS2012 and reinstall VS2010 - unless anyone from TypeMock has a last minute suggestion for me?

Hi Paul,

I'm glad to read that version 7 solves the problems you had with version 6.
Regarding the issue with references that you mentioned in version 7, did you change the references to Typemock in your test projects?

Hi Alex,

No, I didn't change the references - I just installed 7 as a quick test to see if it would get past the issue.

Actually upgrading to 7 isn't feasible for us right now. We have many branches of our product that all run on 6, including maintenance branches. Upgrading to 7 would be a huge undertaking, not to mention the expense. I'm sure we'll end up doing this eventually, but now is not the time for this.

What I'm really looking for is a way to run 6 on my machine with VS2010 while still having VS2012 installed, but it doesn't seem like this is possible.

Paul