At the same time that I was trying TypeMock, I was trying xUnit.NET, however the TestDriven.Net player for xUnit.Net did not seem to allow running more than one test at a time. So, I decided to go back to NUnit for my test, which worked well (I can now run all my test in a "TestFixture").   Since I had a number of tests for my first class in my current project, I decided to setup a coverage analysis of my class from my tests.  TypeMock Isolator has the ability to link to coverage tools (strangely, NCover has not shown as an option for me even though it is installed), so I link to AQtime and ran the tests.  I achieved 100% code coverage (that will not last).

Back to working on the second class, wrote the first test, tried to run the test and TestDriven.Net crashed.  After trying several things, I disabled TypeMock Isolator and ran the test without any problems.  Since I has only three tests using mocks, I just replaced the mocks with a test double and now I can run all my tests.

I think the problem has something to do with the fact that I am developing on a 64 bit system and Visual Studio is 32 bit, so I think there was a conflict there.

Since, I was using TypeMock to reduce the friction in my test, and ended up with more friction, I have decided not to use TypeMock on this project.