T
Tom
While trying to hunt down an Outof MemoryException on our cf 1.0
device, I decided to try using using the limited tools at my disposal
to little effect. I then upgraded to VS 2005 and converted the project
to CF 2.0. What I found was that I could compile for CEPC x86 and then
use a regular .NET profiling/memory tool (ANTS) to profile the
application. OF coulse I run into a big snag when coredll.dll can not
be found, along with any other dll that was p/invoked from the CF
library. Am I wasting my time by going in and finding the proper dll's
to import so that I can use a memory profiler, or is there a simpler
solution to all this?
Tom Kuhn
device, I decided to try using using the limited tools at my disposal
to little effect. I then upgraded to VS 2005 and converted the project
to CF 2.0. What I found was that I could compile for CEPC x86 and then
use a regular .NET profiling/memory tool (ANTS) to profile the
application. OF coulse I run into a big snag when coredll.dll can not
be found, along with any other dll that was p/invoked from the CF
library. Am I wasting my time by going in and finding the proper dll's
to import so that I can use a memory profiler, or is there a simpler
solution to all this?
Tom Kuhn