VS 2003 conection issue with device

[Mickey]

Ever get REALLY stumped?

Working with VS .net 2003, ActiveSync 4.2, and CE 4.2 on device.

I've been working on this for sever days with no issues. I've been able to deploy and run on the device.

After a simple logic error on my part crashed the device while debugging, VS closed the debug session, but the device was locked up.
I had to perform a cold boot on the device.

Now ActiveSync connects to the device, I can copy files, and from device use explorer and all/etc.
But VS won't deploy. I get the "Error: Cannot establish a connection. Be sure the device is physically connected to the development computer."
Already tried the usual suspects (deldesktopcryptkey, proxyports.reg)

Any ideas? I'm sure this is something simple and I just have not had enough caffeine for the day...

 

[Guest]

Does it have a persistent registry? If so delete it, run
DelCryptoKeysDevice and restart.

 

[Mouseman42]

Does it have a persistent registry? If so delete it, run
DelCryptoKeysDevice and restart.

--
Chris Tacke - Embedded MVP
OpenNETCF Consulting
Managed Code in the Embedded Worldwww.opennetcf.com
--










- Show quoted text -

<Its me, mickey, from a different account>
I found out after the first post that this is happening now, even with
different devices (these are Symbol MC3070 scanners, we have 10) none
of the devices are recognized by VS .net 2003, but ActiveSync connects
to each and appears to perform as usual.