I am getting the following exception when my test method is first entered:
Method not found: 'Void TypeMock.ArrangeActAssert.Isolate.ForceInitializeFakeLogProvider()'.
A google search turns up nothing as does a search in your forums. What am I missing??
Bar David | Support Team
I think this may be related to the problem I am having described in question entitled "Tests throw TypeLoadException..." Although I reference a different exception there, initially I was getting the same error you do about ForceInitializeFakeLogProvider.
When I got the same error as you I was using the <ClearMocks> and <Isolated> attributes at class level. To simplify the issue, I removed those and stopped getting that error. But I started getting the error related to TypeMock.ArrangeActAssert.AAAScopes.VBRecordScope on the first test that had any TypeMock code in it.
I suspect that, in both cases, TypeMock is trying to use the code from the C# dll to do the actual mocking, but for some reason is unable to get to it.
I also suspect that whatever solves your problem will solve mine. If you figured out anything, please let me know...
donniedarko - I got the same result with the AAA assembly. (See "CASE 2 - VB and C# hybrid" in the Q&A at https://www.typemock.com/answers/19237/tests-throw-typeloadexception-using-typemock-syntax-version?show=19239#a19239).
The tests work, but as I mentioned in that Q&A it does not allow you to use the TypeMock Test Navigator. I was able to get everything to work, including the navigator, by putting all tests in a C# project, so that might be the better way to go if you are creating new tests.
In the meantime, I am waiting for the fix you mentioned. I have too many old tests written in the VB syntax and I really don't want to have to rewrite them.
We fixed it in version 8.2, which released today.
You can download it from here.