Re: about Visual Studio mobile development simulator

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm telling you that the emulator is *not* a substitute for a real device.
If you say, ah, I don't have device X so I'll use the emulator, you've
really just said, "I don't have device X, so I won't test the code for
that".

Paul T.

"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:193A8CD9-7E7D-498D-8D89-0FD687408469@xxxxxxxxxxxxxxxx
Thank you Paul!


The problem is I do not have all types of real devices (x86, ARM, XScale,
etc.)... but I want to test my code on all these devices, so I need to use
simulator.

As you said, in eVC3/4, the simulator is using a special type of binary
code
standard other than standard x86 binary code standard. Do you know where
could I find official materials (documents, URLs) from Microsoft? I have
tried to find, but can not find any.


regards,
George

"Paul G. Tobey [eMVP]" wrote:

Yes, that's what I mean. The x86 emulator is *not* a true emulator for
the
device. We've already spent more time on the "emulator" than it's worth.
Use a real device.

Paul T.

"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:39BD9A5E-9E6D-495B-8A48-2C9636B7766B@xxxxxxxxxxxxxxxx
Thank you Paul!


I am a little confused about your comment on eVC3/4. Do you mean the
binary
code for eVC3/4 emulator is different from a binary code for target x86
build?

If they are different, I am wondering what are the binary code standard
for
eVC3/4 emulator? A special binary code standard for emulator only?


regards,
George

"Paul G. Tobey [eMVP]" wrote:

No, doesn't work that way for the x86 emulator.

Yes, the ARM emulator actually runs the ARM executable generated by
targeting the real device SDK.

Paul T.

"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:41E98D98-AC40-426B-BB9E-7D83A7B8CB6B@xxxxxxxxxxxxxxxx
Thank you Paul!


Do you mean if I am using eVC3/4, I could copy binary code from/to
simulator
to/from real x86 device?

And also, in Visual Studio 2005, I could also copy binary code for
the
specific processor type of from/to simulator to/from the related
specific
processor type of read device?


regards,
George

"Paul G. Tobey [eMVP]" wrote:

There are two types of emulators floating around. eVC always used
the
x86-based emulator (it acted like an x86 processor running the OS
type
that
you were trying to simulate). VS has the ability to use the ARM
emulator
which emulates not only the device, at the level of the operating
system,
but also the very processor in that device; it allows you to run an
application compiled for the ARM-based device, just as though it
was
running
on the real device.

Paul T.

"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F49106FD-444F-411D-8E3C-BCBF4C524048@xxxxxxxxxxxxxxxx
Thank you Chris!


Your reply answered my question. I just want to confirm one
thing,
you
mentioned "the new tools that use Device Emulator 1.0", do you
mean
the
simulator in Visual Studio 2005?

Since I think in embedded VC3/4, there are only one type of
simulator
(means
you can not select CPU architecture type). Am I correct?


regards,
George

"<ctacke/>" wrote:

With the new tools that use Device Emulator 1.0, if you are
targeting
ARM
architecture, yes it is the same. That doesn't mean you can get
away
without actual on-hardware testing though.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--


"George" <George @discussions.microsoft.com> wrote in message
news:EA5A7A8C-D490-44CB-B070-235FFC567D28@xxxxxxxxxxxxxxxx
Hello everyone,


I am wondering whether the generated binary code on Visual
Studio
integrated
mobile simulator is the same as that of real device (for
example,
real
HP
ARM
iPAD)?

Is the answer to the question (binary code on simulator is the
same
as
that
of read device) the same to all Microsoft mobile development
IDE --
embedded
VC 3/4 and Visual Studio 2005?


thanks in advance,
George














.

Relevant Pages

  • Re: about Visual Studio mobile development simulator
    ... The problem is I do not have all types of real devices (x86, ARM, XScale, ... As you said, in eVC3/4, the simulator is using a special type of binary code ... We've already spent more time on the "emulator" than it's worth. ... Use a real device. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: about Visual Studio mobile development simulator
    ... Do you mean if I am using eVC3/4, I could copy binary code from/to simulator ... And also, in Visual Studio 2005, I could also copy binary code for the ... Each of the SDKs used with eVT comes with an emulator. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: about Visual Studio mobile development simulator
    ... doesn't work that way for the x86 emulator. ... targeting the real device SDK. ... And also, in Visual Studio 2005, I could also copy binary code for the ... specific processor type of from/to simulator to/from the related specific ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: about Visual Studio mobile development simulator
    ... code for eVC3/4 emulator is different from a binary code for target x86 build? ... specific processor type of from/to simulator to/from the related specific ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: about Visual Studio mobile development simulator
    ... The x86 emulator is *not* a true emulator for the ... I am wondering what are the binary code standard ... specific processor type of from/to simulator to/from the related ...
    (microsoft.public.windowsce.embedded.vc)