Beginning to thoroughly dislike VS.Net ppc debugging....

G

Guest

Here it is. The actual transcript from my outout window. What I'm doing is so
basic it is suckeningly furstrating. I have a test program that does nothing
more than display some controls - no magic, no rocket science. Yesterday, I
could run it via the ide and sometimes it would not. Today, it refuses to
run. I've set my emulator to Pocket PC 2003 Emulator. My actual device is an
HP iPaq Hx4700 with Windows Mobile 2003 SE, but I guess that is unimportant
as I'm trying do nothing more complex than try, repeat try, to run this test
program on the emulator. Read on.

------ Build started: Project: Test, Configuration: Debug Pocket PC ------

Preparing resources...
Updating references...
Performing main compilation...

The project is up-to-date.
Building satellite assemblies...
Visual Studio is ready to deploy Test



------ Deploy started: Project: Test, Configuration: Debug Pocket PC ------

Deploying to Pocket PC 2003 Emulator using Emulation Transport
Connected to Pocket PC 2003 Emulator (Pocket PC) running on WCE420X86.
Copying files from 'C:\Temp\Test\bin\Debug' to '\Program Files\Test'
Copying Test.exe



---------------------- Done ----------------------

Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped


Launching Application
Error while trying to run project: Unable to start debugging.

Unable to start program 'C:\Temp\Test\bin\Debug\Test.exe'.

The last line above is a typical MS error message! It knows enough to
respond to the abnormal condition whatever that may be. It knows enough to
tell you "what" went wrong, but if they can go to that extent why can't they
tell the "why" of the problem. It is too vague to be useful. Please agree
with me.

Going forward, why do I have a less than 30% success rate trying to run this
via the emulator? If I've done something wrong, configured something
incorrect, basically f***ed up something, please tell me. As you can see, the
error messages are really very useful. (rolleyes) Maybe someone has
experienced something similar. I really do need a good explanation about the
problem and what to do to get round it. Advice appreciated!
 
P

Peter Foot [MVP]

Does your machine have a permanent network connection? If not you will need
to install the MS Loopback adapter as a network connection is required to
communicate with the emulator. See here for details:-
http://wiki.opennetcf.org/ow.asp?CompactFrameworkFAQ/DebuggingWithoutANetworkConnection


Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups
 
G

Guest

I tried installing the loopback, did a reboot, and hey presto...no difference
whatsoever! Did I miss something else?

It looks like I'll have to stay online to debug.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top