http://msdn.microsoft.com/en-us/library/ms228708%28VS.80%29.aspx
When ActiveSync is not available, Visual Studio 2005 does not automatically copy required connectivity files to the device. Use the following steps to install these files on the device, modify the Visual Studio connection configuration, and establish device security.
The first two steps, preparing the device and Visual Studio, need to be done only once. The last set of steps, setting security and establishing the connection, must be repeated any time you want to connect from a new instance of Visual Studio.
To prepare the device for connecting
-
Using whatever connection with the device you have, copy the following files to the /Windows/ folder on the device. These files are located on the development computer by default at /Program Files/Common Files/Microsoft Shared/CoreCon/1.0/Target/wce400/<CPU>.
-
Clientshutdown.exe
-
ConmanClient2.exe
-
CMaccept.exe
-
eDbgTL.dll
-
TcpConnectionA.dll
-
-
From the command prompt on the device, run conmanclient2.exe.
-
Determine the IP address of the device.
To prepare Visual Studio for connecting
-
On the Visual Studio Tools menu, click Options , then click Device Tools , and then click Devices .
-
Select Windows CE Device , and then click Properties .
-
To the right of the Transport box, click Configure .
-
In the Configure TCP/IP Transport dialog box, select Use specific IP address , and then type the device IP address.
-
Close the dialog boxes.
A message box might appear prompting you to reset your device. If so, a soft reset is sufficient.
To set security and establish the connection
-
At the command prompt on the device, run cMaccept.exe.
-
Within three minutes, connect to the device.
If you establish your first connection within three minutes, you can continue deploying and debugging indefinitely as long as you are using the same Visual Studio instance. If you need to connect from another instance of Visual Studio, you need to perform these security steps again.
Security Note You can eliminate the cMaccept step by disabling security on the device. To do so, use the Remote Registry Editor to set HLKM/System/CoreConOverrideSecurity = 1 DWORD value. Disabling security exposes your device to malicious attack and is not recommended unless you have provided appropriate safeguards.
See Also
Concepts
Remote Tools for Device Projects