VS2003 and WM 6.0 debugging

  • Thread starter Thread starter Markus Humm
  • Start date Start date
M

Markus Humm

Hello,

I'm using VS2003 for development and won't right now upgrade to
something new as it would require CF 2.0 or higher I assume.

New devices today have CF 2.0 pre installed, esp. WM6.0 devices.
But: I cannot debug on them! If I try I get a message on the
device when it tries to run the app. but:

a) the message is very long, covering nearly the entire screen
b) it is displayed way to short so I can't read it

Now my questions:

1. how can I debug on those devices?
2. who designed this message and esp. that it vanishes so fast?
This person should also vanish...equally fast! ;-)

Greetings

Markus
 
Since you're running against a different version of the .NET CF than what
VS.NET 2003 knows about, it can't effectively debug. I think that's what
the message is telling you. You get the same message if you try to run your
..NET CF 2.0 program in the debugger, against a device that has .NET CF 3.5
in ROM. The IDE doesn't know about that version of the run-time, so you
can't debug against it. If you had VS2005, you'd be able to do what you're
talking about, since it handles both .NET CF 1.0 and 2.0.

Paul T.
 
Paul said:
Since you're running against a different version of the .NET CF than what
VS.NET 2003 knows about, it can't effectively debug. I think that's what
the message is telling you. You get the same message if you try to run your
.NET CF 2.0 program in the debugger, against a device that has .NET CF 3.5
in ROM. The IDE doesn't know about that version of the run-time, so you
can't debug against it. If you had VS2005, you'd be able to do what you're
talking about, since it handles both .NET CF 1.0 and 2.0.
Click to expand...

Ah ok. But: why is a message as long as this only displayed 1-2 seconds
so that you cannot by all means read it? Who designed it this way?

Greetings

Markus
 
I can't answer that. I've never tried to used that particular combination.
If you try to debug a .NET CF 3.5 application with VS2005, a similar
combination of 'you can't do that' items, you get a suitable message on the
VS device that tells you what's wrong.

Paul T.
 
Back
Top