Deployment problems...

  • Thread starter Thread starter Brian H
  • Start date Start date
B

Brian H

Hi all,

When I opened my project yesterday, I found that I could no longer deploy it
vis VS.NET 2003 to my device (iPaq 2215). There's been no new software
installed, so I'm at a loss as to the problem.

I repaired VS.NET 2003. (No help)
I reinstalled Activesync (no help) -- but it does sync fine and I can browse
the device fine.
I repaired VS.NET 2003 again, no help.

I've plugged the device into another laptop, it deploys fine. How can I fix
this?

Thanks for any suggestions,

Brian
 
Brian,

What is the exact error ?

Can you "Connect to device" from Tools ?
Is the app you are trying to deploy actually running in memory on the ipaq ?

James McCutcheon
 
Thanks James...

The error is: unable to connect ... so, nope :) cannot connect from the
tools menu.

It dawned on me that two days ago I did change my windows domain password.
When I log on via a local account, I can deploy fine. So a good bet is that
the password change screwed things up. I've been playing with a lot of the
utilities in the VS.NET/CF folders (such as DelDesktopCryptKey.exe) but so
far, nothing has worked. At the very least I can use a local account to
debug, but it seems like there must be a solution in front of my face...

Thanks,
Brian
 
Thanks very much James --

I tried all the reg stuff, no luck -- but I did get it to work. Here's what
I did (and what I didn't do): First, in my earlier steps of debugging, I
tried changing the settings (within VS) to connect to the device via IP
address, instead of obtaining the IP automatically. That didn't work. But
I didn't change it back after running the applications to delete the desktop
and device keys.

When I deleted the keys on the device, I could see that -- when I clicked
deploy application -- the key would get recreated. But VS would still
report a deployment issue. Once I fixed the connection settings in VS, all
worked fine.

So for future people who have this problem, download the WinCE Utilities for
Visual Studio, and go through each of the steps in the readme until it works
:)

Thanks for your help,
Brian
 
Back
Top