Very Computer

I am using eMbedded Visual Studio 3.0 and Active Sync.  

I have created a hello world application that I can build
and debug (from Win2k).  It works just fine.  

But, when I try to debug my real application, I get an
error message popup on the Win2k side in the de*
saying "Please check the remote executable path and file
name from your project setting".  Then, when I press the
ok button on the message box, the de* is detached
from the remote process as though it thinks the process
failed to start.  However, the executable runs on the CE
device!  

I have probably tried this 50 times and it behaved this
same way, but while typing this message and trying one
more time just to get the exact error message, it worked.
But, now it is not working again.

The settings referred to in the error message are grayed
out and this is apparently due tot he fact that this is an
executable (.exe) file.

Can anybody tell me what is wrong?  Thanks.

You can try these steps:
1.In eVC, go Tools->Configure Platform Manager.Pick up the device type you
have and click Properties.
   See you can connect you device to desktop via either TCP/IP,maybe you
need click Advanced button here and
   setup to ActiveSync connection.
2.Hook up your device to desktop...
3.Build the DEBUG version for you application and press F5 to debug it.

Quote:> I am using eMbedded Visual Studio 3.0 and Active Sync.

> I have created a hello world application that I can build
> and debug (from Win2k).  It works just fine.

> But, when I try to debug my real application, I get an
> error message popup on the Win2k side in the de*
> saying "Please check the remote executable path and file
> name from your project setting".  Then, when I press the
> ok button on the message box, the de* is detached
> from the remote process as though it thinks the process
> failed to start.  However, the executable runs on the CE
> device!

> I have probably tried this 50 times and it behaved this
> same way, but while typing this message and trying one
> more time just to get the exact error message, it worked.
> But, now it is not working again.

> The settings referred to in the error message are grayed
> out and this is apparently due tot he fact that this is an
> executable (.exe) file.

> Can anybody tell me what is wrong?  Thanks.