Re: WinCE 6.0 BSP (CEPC) for Virtual PC

Tech-Archive recommends: Speed Up your PC by fixing your registry



The large question is "why?" What purpose would this VPC server? There is
already an emulator that can be used as a target. Trying to get a CE OS
running on a VPC would be a lot of work for seemingly little (or no)
benefit. Just install the emulator BSP, generate an image and have the devs
use the that emulator as a target. In many cases, it would be less
expensive to just go buy each developer an ICOP eBox target than to even
spend the time trying to get the emulator builds generated and deployed to
the devs. They are inexpensive and have working CE images already loaded,
plus you can adjust the contents down the road if you so choose with PB.

The reality is that I've been doing non-WinMo CE development for a little
while now and I haven't loaded up an emulator in years. The times I have
were almost always to test something emulator related, not platform related.
Emulators can be useful, but you really have to treat it as a product itself
when developing your platform, and few OEMs go to that trouble since the
payback is often negligible.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com




"GJ" <GJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4982C5A8-C33C-48CD-B6EB-0591CD1D670D@xxxxxxxxxxxxxxxx
Thanks for the info. I do understand that CE doesn't support the full
.NET
Framework, and exploring what is "missing" is one of our objects in doing
this "pre" development work.

However, I do still believe that a CEPC VPC would be a valuable tool to
have
at our finger tips. We may find that out differently once we get into
full
development, but all avenues should be explored.

Is it that difficult to do that no one has done it, even as an exercise?
I
did find a CE 5.0 VPC on the web, so it can't be that great of a leap to
produce a WinCE 6.0 VPC.

"Paul G. Tobey [eMVP]" wrote:

You won't be using .NET Framework 3.0 for CE development. The full .NET
framework does not run on Windows CE. Windows CE can, optionally, be
equipped by the device OEM with .NET *Compact Framework* 1.0, 2.0, or
3.5.
VS2008 can be used for development with .NET CF 2.0 or 3.5, so your tools
are fine, if your OS is set up correctly.

No, application developers don't need Platform Builder. Once you've
generated an OS image and the corresponding emulator image, Platform
Builder
allows you to generate a device SDK for that OS/device. This can then be
installed on any VS2005/2008-equipped system, where it can be used.

Paul T.

"GJ" <GJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5897EEBC-70F1-4722-A0B7-E41BF21C882A@xxxxxxxxxxxxxxxx
Thanks Paul for your message. The software development group is using
VS2008
and developing in C# and .NET 3.0. So, each developer would have to
have
VS2005 w/PB installed also, even though they have no intension of
building
images. Other non-software team members would have to have VS2005 w/PB
installed to test drive or demo the applications. I do see the value
in
using the emulator for some aspects of the software development, but in
other
aspects it's a hinderance. I would have a hard time convincing
non-software
developers into installing VS2005 + SP1 + PB just to look at our
applications.

"Paul G. Tobey [eMVP]" wrote:

Platform Builder has an emulator target. I think that makes more sense
than
trying to run the OS on a PC within a PC. Download the Platform
Builder
evaluation version via the www.microsoft.com/embedded page, install
VS2005
Pro and the evaluation and work through some of the tutorials in the
help.
That will give you the ability to build some sort of an emulator image
which
you can then play with to understand how application development
works.

There's also the no-Platform-Builder option, if you aren't going to be
building Windows CE for your target hardware later. Install VS2005
Pro
or
better and one of Microsoft-provided SDKs. Something like Windows
Mobile
6
would do. That would give you an emulator target that you could play
with.
Some of the APIs in WM6 are not available to generic Windows CE
platforms,
but, if you carefully avoid those, you should be able to familiarize
yourself with what you have to do.

Paul T.

"GJ" <GJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C109E8C-4AB5-4DC1-9C66-463DC4EA9460@xxxxxxxxxxxxxxxx
We are considering WinCE 6.0 for a new project, and while the
hardware
guys
are out looking at/evaluating platforms, I would like to get
familiar
with
WinCE 6.0 application development. My thought is to run WinCE 6.0
in a
Virtual PC environment (or Vmware). I've searched the web and found
vague
references to being able to do this. I will buy a commercial
product,
and
if
one isn't available I would attempt to build my own BSP (not
desireable
at
this point).

I can't imagine that I'm the only one who would like to do this. I
would
greatly appreciate any info on this subject.

Thanks!








.



Relevant Pages

  • Re: WinCE 6.0 BSP (CEPC) for Virtual PC
    ... You can do POC code with the emulator - again, just like the VPC. ... be targeting say ARM architecture hardware, one could argue that emulator is ... CE platform development is not easy (anyone who tells you otherwise, ...
    (microsoft.public.windowsce.embedded)
  • Re: WinCE 6.0 BSP (CEPC) for Virtual PC
    ... and a pretty low cost. ... I don't see what you feel the VPC would ... magically provide that the existing emulator does not. ... BSP and platform readily available. ...
    (microsoft.public.windowsce.embedded)
  • Re: WinCE 6.0 BSP (CEPC) for Virtual PC
    ... what I knew about Windows CE to it was a waste of time. ... VPC as a target and it works VERY well. ... Just install the emulator BSP, generate an image and have the ... when developing your platform, and few OEMs go to that trouble since the ...
    (microsoft.public.windowsce.embedded)
  • Re: WinCE 6.0 BSP (CEPC) for Virtual PC
    ... when you install the WM6 SDK), ... was hoping there was a CEPC VPC out there... ... will be using the WinCE emulator. ... VPC as a target and it works VERY well. ...
    (microsoft.public.windowsce.embedded)
  • Re: question about vb.net support in ce 6.0
    ... You can target the emulator from your managed code project directly by ... VB.NET program *to the operating system*. ...
    (microsoft.public.windowsce.embedded.vb)