CE 4.2 Solution Deployment Woes

[jminiman]

Really have little clue as to what's going on. I have a multiple
project solution. I have two identical Windows CE 4.2 devices, but
with a newer ROM image (still CE 4.2) on one. On the first device, I
deploy my solution (as CE 5.0 projects) without any errors. On the
second, I get:

An existing connection was forcibly closed by the remote host.

Both devices are untrusted and totally unlocked to debugging. But I'm
trying to figure out whether it's my desktop (ActiveSync 4.2.0) or
something on the IMD which is causing the issue. Any tips as to how I
can debug the problem? The error message above means nothing to me!

 

[Guest]

Is this a plain CE 4.2 device? Does it have a persistent registry? Are you
pushing to RAM or a persistent FS location?

 

[jminiman]

Correct. This is a generic, CE 4.2 device running CF.NET 2.0 SP1
(though the deployment process should not depend on the level of CF,
since I can deploy to a device running an older, CF 1.0-in-ROM image
without errors).

It does not have persistent registry. It is being deployment to
\Program Files in RAM.

--jsm NG*

 

[Guest]

Hmm, I was going to guess the persistent registry had device authentication
key info on the failing device that did not match the PC (this happens if
you restart and lose all files but the registry info remains). Since that's
not possible here I'm out of quick ideas.