debugging problems with Activesync/visual Studio .NET 2003
I have a recurring problem debugging on my device with Visual Studio .NET, and I'm beyond desperate to get it resolved. I am able to connect to my device using Activesync. I can copy files back and forth. I have put the appropriate toolhelp.dll file in the windows directory. I have set the appropriate CPU type, and gone through every Microsoft tutorial I could find. No matter what I do, when I try to connect to the device it says the device is not physically connected. If this problem didn't exist, I would have been finished with my project months ago. PLEASE HELP!
Hi Geoffrey,
Not able to figure out the exact scenario and environment. Please share the following information.
- Active Sync Version
- Device name and CPU
- Using managed app or native
- Full Error message
- Is it giving the same error in F5, Ctrl-F5 and deploy conditions?
- Is it working with Emulator?
Regards
Gaurav
i have the same problem with this equipment:
- ipaq 3970 (pocket pc 2002)
- ipaq 6515 (pocket pc 2003)
- activesync 3.80 and 3.71
- win xp sp2
- visual studio .net 2003
It works fine with the emulator. I am using ActiveSync 3.8, though 3.7.1 didn't work any better. I am using an armv4t called a LittleArm. I am building a VB.net program, so it is managed. When I attempt to Connect to Device(keep in mind that I am fully connected via Activesync at this point), Visual Studio says "establishing connection" for a while, and then pops up an error message that says "cannot establish a connection. be sure the device is physically connected to the development computer". If I try to run it, it looks like it is attempting to copy a file, and then it says there are deployment errors.
I have installed the utilities, and I have run the ProxyReg script, and neither of these worked.
Anything else I might have missed?
