problem with clr profiler

[irioja]

I try to debug a netcf application with clr profiler and always appears at
any moment the message "Unable to connect for 45 seconds. Please verify the
remote device is connected". I use the WM 6.0 emulator and the emulator has
the netcf 2.0 and netcf 3.5. The application is made with netcf 2.0 and at
the first moment profiler connect with device and launcht it. Please any
ideas?
thanks in advance

 

[Alberto Silva, MVP]

How are you connecting to the emulator, choosing it directly from the list
of choices of emulators, or choosing "Windows Mobile 6 Professional Device"
and cradling it on the Device Emulator Manager via ActiveSync/WMDC using
DMA? If you have tried only one of these options, can you try the other way?

--

Alberto Silva
http://www.moving2u.pt - R&D Manager
http://msmvps.com/AlbertoSilva - Blog
Microsoft MVP - Device Application Development

I try to debug a netcf application with clr profiler and always appears at
any moment the message "Unable to connect for 45 seconds. Please verify
the remote device is connected". I use the WM 6.0 emulator and the
emulator has the netcf 2.0 and netcf 3.5. The application is made with
netcf 2.0 and at the first moment profiler connect with device and launcht
it. Please any ideas?
thanks in advance


__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4405 (20090908) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4405 (20090908) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[Chris Tacke, MVP]

Have you tried a real device? Last I checked the emulator wasn't a
supported target (the profiler couldn't attach to it).


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

 

[Alberto Silva, MVP]

It should work, I've done it 2 or 3 months ago, but I'm not sure how have I
connected the .NET CF CLR profiler to the emulator instance.

--

Alberto Silva
http://www.moving2u.pt - R&D Manager
http://msmvps.com/AlbertoSilva - Blog
Microsoft MVP - Device Application Development

Have you tried a real device? Last I checked the emulator wasn't a
supported target (the profiler couldn't attach to it).


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com




__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4406 (20090908) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4406 (20090908) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[irioja]

I upgrade the application to netcf 3.5 and the profiler runs but not with
netcf 2.0 . In activeSync I use DMA.

 

[Alberto Silva, MVP]

Hi,
If you're using the .NET CF Profiler came with the .NET CF 3.5 Power Toys,
I'm not sure if the .NET CF 2.0 is supported.

Depending on your purpose, you may also take a look at the Eqatec Profiler,
wich supports the .NET CF 2.0 & 3.5 and by the way, is free:

http://www.eqatec.com/tools/profiler

--

Alberto Silva
http://www.moving2u.pt - R&D Manager
http://msmvps.com/AlbertoSilva - Blog
Microsoft MVP - Device Application Development

I upgrade the application to netcf 3.5 and the profiler runs but not with
netcf 2.0 . In activeSync I use DMA.

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4416 (20090911) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[Paul G. Tobey]

Yes, Alberto is right. In fact, many of the Microsoft tools prefer their
own version of the run-time to this extent, not working, or not working
correctly with other run-time versions.

Paul T.