How can I run my Windows CE project from within Visual Studio (2003)?

Question

I'm working on a legacy app that needs to be continued in VS 2003; I cannot effectively debug it, though, because when I try to run it, I get the following dialog:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Deploy

Choose the device to target. If the .NET Compact Framework is not already on the selected device, it will be deployed along iwth your application.

Pocket PC 2002 Emulator
Pocket PC Device
Windows CE .NET Device
Windows CE .NET Emulator (Default)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I am running this (VS 2003) in XP Mode (Virtual Machine) on Windows 7. I do not have a connection (from XP Mode) to the device - a Symbol/Motorola PDT 3090 - so I get, "Unable to connect" when trying to run/debug/deploy in VS 2003.

What has been the case up to now is the developer would build the binary, adding debug messages, and then copy the binary over to the device and run it. Rather than continue this method, I would prefer to be able to debug it from within VS 2003. Is there a way to do this? None of the options (Pocket PC 2002 Emulator, etc.) seem to work...the device is attached to the computer via a usb. The Emulators won't work because they don’t have the necessary hardware (barcode scanner). So I need to use one of the *Device options, but have not been able to connect the usb port to XP Mode.

Does anybody have any ideas on how to debug without the constant copying-and-replacing of binaries, and the use of "show message"?

UPDATE

Alternately, if I can't run the app from within VS 2003 / XP Mode as an emulator, it would also be fine to run it on the attached Motorola handheld, attached via usb cable from the cradle to the desktop computer; I prefer the former, for the debugging capabilities afforded, but even the latter would be better than my current predicament (copying the files to the handheld device, detaching it from the computer, attaching it to the belt printer, firing it up, testing and repeat ad nauseum ad infinitum). ASAP (within two hours), I will set a bounty on this question.

UPDATE 2

If I try to run from VS 2003 in an emulator, and select "Windows CE .NET Emulator (Default)", I get:

"Emulator for Windows CE will not run within another copy of Emulator for Windows CE. You just had to try, didn't you?"

?!? Is it saying this because I'm in a VM (XP Mode) session?

Then I select "OK" (the only option), and get, "There were deployment errors. Continue?" That trick never works; it even causes the build to fail (a rebuild fixes that, though).

UPDATE 3

Perhaps my problem with not being able to debug by connecting to the device itself is related to this msg I saw when booting up this morning (but I don't know what to do about it, IF this is the problem - do I need to search for a new driver for the Motorola MC3100?):

Devices or applications disabled.
Virtual PC/Windows CE Emulator will cause Windows to become unstable. Windows has prevented these drivers from loading. click here for more details.

The "more details" are:

Virtual PC/Windows CE Emulator 
Microsoft 

--------------------------------------------------------------------------------

Issue Description: 

    A driver is installed that causes stability problems with your system. This driver will be disabled. Please contact the driver manufacturer for an update that is compatible with this version of Windows. 

    Contact Information: 

    Web Site: http://go.microsoft.com/fwlink/?LinkId=26320
    Telephone: 1-800-936-5800

That link (http://go.microsoft.com/fwlink/?LinkId=26320) ended up as: "Internet Explorer cannot display the webpage"

UPDATE 4

There is some headway (or perhaps just false hope) on the connecting to the device front:

I have 4 USB ports on my desktop machine. I plugged the USB cable into the 3rd from the top for the first time a bit ago. It then said it was recognized, and ActiveSync was finally able to make a connection.

So I then tried deploying the app again. The fourth option (the default - C.E. Device Emulator) failed as always. So did the penultimate choice (C.E. device). The second option, though (Pocket PC device), seems to possibly be working.

However, I got a cryptic err msg that just said:

#183:

I dismissed that and since then (it's been a good ten minutes now), the bottom of the VS Output windows has been saying "Launching Application" (with a blinking cursor beneath it) and the task bar has been claiming "Deploy started..."

Whether that is really of any value, though, it doesn't appear to be, as I am just "stuck" there...

I've got a non-VM XP machine with MS ActiveSync 4.5 and it connects fine to that model of device. I assume it is a VM issue. — tcarvin
I would prefer to run it in an emulator rather than actually on the device while debugging, anyway. — B. Clay Shannon-B. Crow Raven
Any reason for that? If you have access to the hardware I would recommend developing and debugging against the device instead. — tcarvin
That's the problem: the XP Mode MV I have to use for development cannot "see" the usb port that connects to the handheld device. — B. Clay Shannon-B. Crow Raven
Got it, you are in a tough spot. Some versions of ActiveSync and devices supported wireless connections, but I think you had to create a partnership first and you cannot even do that without being cabled to the PC. — tcarvin

jp2code jp2code · Accepted Answer · 2013-02-06T14:26:40

Windows CE .NET Emulator (Default)

This should be the one you want, if you are running Windows CE.

The Barcode Reader takes the code and converts it to a string for you, so your code will never need to "decode" a barcode.

So, when you are testing your software using the CE Emulator, simply select the textbox you want to read the barcode to, and type that value in using your keyboard.