Can these two be used together? Because normally when creating objects in an OpenAccess project you need to start transactions and data is automatically saved to the database.
My company uses TypeMock as our isolation tools in our unit tests. The great thing about TypeMock is that it has almost no limitation on what it can mock. This freedom however comes from a design choice that is also the greates weakness of TypeMock: it is a Profiler.
The problem we have is that since the .NET CLR can only have one profiler attached at a time, other profilers must go through TypeMock to work. For another profiler to work while TypeMock is running it must be supported by TypeMock. This is a problem when new versions of profilers are released, like the 4.0 version of dotTrace, or when a great profiler isn't supported at all, like Ants from red gate. I'd like to choose which profiler to use based on price, features and how it suits my needs, not based on which one TypeMock likes.
Also, since TypeMock works as profiler and intercepts and alters calls by using the profiling API it can have some pretty odd bugs. Like, for example, it will crash if you try to isolate a call using the Microsoft Entlib Data block in an x64 process.
My three questions about JustMock are:
1. Is it also a "profiler"'?
2. If JustMock is also a profiler, how have you solved the issues with it working together with other profilers?
3. If JustMock is also a profiler, will you strive to make it just as stable in an x64 process as in an x86 process?