What do you suggest to use for code coverage on 64-bit environment. It seems that NCover supports 64-bit only in Enterprise version which seems to be quite expensive. Or isn't it? What are people using on 64-bit systems for .NET code coverage?
EDIT: I am aware of the CorFlag workaround. I would like to know what others are doing/using. Are you using something else or are you using NCover (free edition) with CorFlag trick?
Google found me this: http://rabdullin.com/how-to-run-free-ncover-on-a-64-bit-machine/
David, I recently took a look at the open source Part Cover. It too has issues with 64 bit, the work around also being corflag, provided by a Sharp Develop contributor, who package and integrate with Part Cover.
The snk file is in in their SVN repo.
Is NCover Enterprise worth it? I guess only you can really make that decision. There is a 21 day trial. If you can't justify the outlay Part Cover could help you.
It appears that all .NET code coverage tools use c++ packaged as COM. Unless somebody can come up with a managed code implementation, I suspect a 64 bit build will always be required.
What about .Net Coverage Validator? It works with all version of .Net and works with both 32 bit and 64 bit versions. http://www.softwareverify.com/dotNet/coverage/index.html
A managed implementation of a code profiler is not possible (same for Java as well) as then the profiler would instrument itself. Thus all .Net/Java profilers are native unmanaged code written in whatever language you want (although typically C or C++).
Both the Classic and Complete versions of NCover support 64 bit.
Thank you,
Joe Feser
See SD C# Test Coverage for a tool that handls 32 bit and 64 bit versions of C# with aplomb.