Compact Framework CLR Profiler

[Guest]

I am trying to make use of the .NETCF CLR
profiler that was recently released separate from the 3.5 beta compact
framework sdk:

http://www.microsoft.com/downloads/...14-A27D-4148-BF01-86C2E0953EAB&displaylang=en

I have been able to use it to successfully launch a simple example
application (both via IP and via active sync), but shortly after the
application starts up, the profiler
running on the desktop throws this error - confusing since the application
actually pulls up after using the profiler to start it:

This operation returned because the timeout period expired. (Exception from
HRESULT: 0x800705B4)

I have been able to get the Remote Performance Monitor tool to work,
but not the profiler, and I would appreciate any help anyone might be able to
give.

 

[Fabien]

Hi,

I have tried it too and it works fine for me.
http://fabdecret.blogspot.com/2007/09/cf-35-debug-tools.html

Fabien Decret (Device Application Development MVP)
Windows Embedded Consultant

ADENEO (ADESET)
http://www.adeneo.adetelgroup.com/ | http://fabdecret.blogspot.com/

 

[Antonio Prados]

Well... I have the same problem: timeout period expired after my
application starts up.
Maybe is something only related with ActiveSync, I don't know.
Then I must hard reset the device because every time I restart the
application a message appears:"Do you want to continue profiling?" and
some files are created. I delete them, but they appear when I restart
the application. A soft reset does not help...

Any help would be appreciated.