No, the communication streams are completely different for VS.NET and eVC.
They don't use the same components on the device at all. If you have *no*
ability to use ActiveSync with your device, you'll have to change the OS
configuration and rebuild the OS.
If you *can* use ActiveSync, start by establishing an ActiveSync connection
to the device. Install the Windows CE tools for VS.NET. I don't have the
link handy, but they can be found by searching for something like "visual
studio windows ce tools" at
www.microsoft.com/downloads. Once you've
installed them, you should have the Select Windows CE Device CPU on the
Tools menu in VS.NET. Run that and select the right CPU for your device.
After that, you will have to set the correct configuration for the device
via the same place where you were setting the communication protocols
before: Options | Device Tools | Devices. Choose the Windows CE Platform
from the drop-down list and select Windows CE.NET Device. Choose the
Configure... button next to the TCP Connect Transport and select the Obtain
an IP address automatically item. Hit OK. Choose the Connect button and
the connection should be established (via ActiveSync).
If you *can't* use ActiveSync, you'll have to be able to run a UI program on
the device called the Smart Device Authentication Utility program. You add
this to your OS from the catalog in Platform Builder. It can be found at
Core OS | Display based Devices | Applications and Services Development |
..NET Compact Framework. Once the OS is built, you'll find a program called
sdauthutildevice.exe in the \Windows directory. Run it and select the Start
button. This creates a listening socket that the corresponding program on
the desktop can connect to and set everything up. From the VS.NET Tools
menu, run the Smart Device Authentication Utility item, enter the IP address
of the device (which is shown in a list box when you run the device end of
the utility), and click Set Up Device. When the device is found and set up,
you can close the desktop side program and the device-side program will be
closed automatically. Now, return to the device options in VS.NET. Again,
select the Configure button for the target device, but this time select the
Use specific IP address option and enter the IP address you entered in the
Smart Device Authentication Uility above. Hit OK and again check the
connection with the Connect button. If everything is fine, you should be
able to deploy your solution to the device.
Paul T.
