Vs2005 WinCe Emulator

I may have missed something but I did not see an emulator in the Vs2005 for
WinCe. Am I making a error or is there an Add-in available that adds an
Emulator for Vs2005 for WinCe?

Thanks.
--
John Olbert

Daniel
Sat Dec 17 12:25:12 CST 2005

You are not missing anything, there isn't a CE 5.0 emulator for VS2005.

Some people have had success with debugging with the stand alone x86
emulator (I haven't but can at least run CF 2 apps on it). See the link in
the last para:
http://www.danielmoth.com/Blog/2004/12/visual-studio-wince-emulators.html

If you have PB you might be able to generate an SDK for VS as described here
(again, I have done this with PB4.2 but not PB 5.0 yet):
http://www.danielmoth.com/Blog/2005/01/pb-sdk-for-vs.html

I wouldn't be surprised if we saw a VS2005 emulator as a download at a
future date from MSFT.

Cheers
Daniel
--
http://www.danielmoth.com/Blog/

"John Olbert" <someone@snet.net> wrote in message
news:704EA0E6-91B8-493B-9442-ECA35E3B6D8B@microsoft.com...
>I may have missed something but I did not see an emulator in the Vs2005 for
> WinCe. Am I making a error or is there an Add-in available that adds an
> Emulator for Vs2005 for WinCe?
>
> Thanks.
> --
> John Olbert
>

John
Mon Dec 19 06:57:08 CST 2005


> Some people have had success with debugging with the stand alone x86
> emulator (I haven't but can at least run CF 2 apps on it). See the link in
> the last para:
> http://www.danielmoth.com/Blog/2004/12/visual-studio-wince-emulators.html

I have had success in connecting a the x86 emulator to VS 2005 using this
process:

http://msdn2.microsoft.com/en-us/library/ms228708(en-US,VS.80).aspx

I had to launch the emulator with 'virtual switch' to allow incoming TCP/IP
connections.

> If you have PB you might be able to generate an SDK for VS as described
> here (again, I have done this with PB4.2 but not PB 5.0 yet):
> http://www.danielmoth.com/Blog/2005/01/pb-sdk-for-vs.html

I have not got this to work at all (with VS 2005). In fact, once installed,
my SDK crashes VS2005 until the SDK is uninstalled.

> I wouldn't be surprised if we saw a VS2005 emulator as a download at a
> future date from MSFT.

Ideally we need a BSP for PB 5.0 so we can build images for the new ARM
emulator. However, using x86 and TCP/IP as above is a good compromise

Cheers,
- John

someone
Mon Dec 19 16:30:03 CST 2005

Thanks.
It is strange that in the efforts to push forward WinCe (our inhouse pcb is
WinCe based) they did not have the WinCe Emulator. Of all the items I would
have thought that the first to provide.

Again, thanks.
--
John Olbert



"John Roberts" wrote:

>
> > Some people have had success with debugging with the stand alone x86
> > emulator (I haven't but can at least run CF 2 apps on it). See the link in
> > the last para:
> > http://www.danielmoth.com/Blog/2004/12/visual-studio-wince-emulators.html
>
> I have had success in connecting a the x86 emulator to VS 2005 using this
> process:
>
> http://msdn2.microsoft.com/en-us/library/ms228708(en-US,VS.80).aspx
>
> I had to launch the emulator with 'virtual switch' to allow incoming TCP/IP
> connections.
>
> > If you have PB you might be able to generate an SDK for VS as described
> > here (again, I have done this with PB4.2 but not PB 5.0 yet):
> > http://www.danielmoth.com/Blog/2005/01/pb-sdk-for-vs.html
>
> I have not got this to work at all (with VS 2005). In fact, once installed,
> my SDK crashes VS2005 until the SDK is uninstalled.
>
> > I wouldn't be surprised if we saw a VS2005 emulator as a download at a
> > future date from MSFT.
>
> Ideally we need a BSP for PB 5.0 so we can build images for the new ARM
> emulator. However, using x86 and TCP/IP as above is a good compromise
>
> Cheers,
> - John
>
>
>

John
Tue Dec 20 06:04:43 CST 2005


> It is strange that in the efforts to push forward WinCe (our inhouse pcb
> is
> WinCe based) they did not have the WinCe Emulator. Of all the items I
> would
> have thought that the first to provide.

If you have your own build of WinCE then a WinCE emulator image from MS
might not be want you want anyway. It is unlikely to have the same
components or options that match your device and therefore may not be that
useful. What you really need to be able to do is build emulator images that
match your device. You already have the ability to do that for the x86
emulator and this can be used with VS2005 and CF 2.0. What's lacking is the
ability to create ARM emulator images and the full integration that this has
with VS2005.

There is some debate about whether MS should provide a generic Win CE image
and how useful that would be. I guess it depends on what sort of
applications you are building, the nature of the device you are targetting
and whether your in-house team use Platform Builder or not.