Re: ABOUT Microsoft Windows CE .NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

There are so many things that you need to know that I hardly know where to
start...

You can develop applications for Windows CE.NET-based devices using Visual
Studio .NET 2003 Pro or higher or eMbedded Visual C++ 4.0 (a free download
from Microsoft). VS.NET 2003 allows you to write managed code applications
using either C# or VB.NET (*no* C++). eVC++ 4.0 allows you to write native
C/C++ applications. So, if you know what language you have to use, you can
choose your development environment. In VS.NET 2003, applications targeting
Windows CE are called "Smart Device Applications". Note that managed code
is also only supported in Windows CE.NET 4.1 and higher, if I recall
correctly, so, if your device runs CE.NET 4.0, you can *only* use eVC++ 4.0.
Your device vendor should give you an SDK for eVC for that development and
may have one for managed code development, also. Consult with them for more
information.

Since Windows CE is a modular operating system, no, there is not *an*
emulator for it, because 'it' is different on every device. You might have
one device that has a screen, keyboard support, etc. and another device with
no screen, no keyboard support, maybe no network support, and they can both
run Windows CE, so every device (unless it's a standard configuration, like
Pocket PC), would need to have its own emulator. There's a so-called
Standard SDK that you can install for eVC that has an emulator for a
mythical device with screen, and a few standard components in it, but it's
not really 'standard' and you should consult your device OEM about an
emulator for the real device (Pocket PC SDK has one, as do the other
MS-supplied SDKs). VS.NET 2003 also has an emulator for Windows CE.NET that
has a similar set of capabilities to the Standard SDK emulator for eVC.
Again, though, just because something works in the Standard SDK emulator
does *not* mean that it will work on the real device, so you should try to
stick with the real device's SDK.

This newsgroup is *only* appropriate for managed code questions when using
C# or VB.NET on Windows CE. For eVC++ 4.0 questions, see
microsoft.public.windowsce.embedded.vc.

Paul T.

"roni" <xservicex@xxxxxxxxxxx> wrote in message
news:dfotv5$lnq$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> hi.
>
> i got new project,to develop application in csharp on small mobile
> computer
> (X600 of politess ).
>
>
> my question is,from where to start ?
> anyone can recommend about good link,that talks about developing
> applications for wince.net .
>
> one other important thing, is there emulator for wince.net ? so i can test
> my application on desktop before upload to the mobile computer ?
>
>
> in the dotnet environment,this type of applications calls "smart phone"
> application ? "mobile application" ?
>
> this news groups is for this type of applications ? or there is other news
> group..
>
> have a nice day.
>
>


.

Relevant Pages

  • Re: Noob question.
    ... This is because there's no such thing as *a* Windows CE emulator. ... device-specific SDK to have a device-specific emulator. ... address (you have to be sure that the target device is running ConmanClient2 ...
    (microsoft.public.windowsce.app.development)
  • Re: CE emulator for VB 2005
    ... My preference is to target Windows Mobile... ... .."Paul G. Tobey " <p space tobey no spam AT no instrument no spam DOT ... Microsoft finally realized that having something called Standard SDK made people think that developing for that meant that the code would work on CE devices, ... there's no emulator that makes sense for that device. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: CE emulator for VB 2005
    ... best, 1/2 right, as there's no such thing as a Standard Windows CE ... finally realized that having something called Standard SDK made people ... If you have a target Windows CE device, then the SDK *for that device* is ... emulator for the device, you can use it. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: sdk question
    ... I can see the target CPU on remote file viewer so activesync is working. ... Windows CE is not like desktop Windows. ... SDK, but that's the exception, when you're talking about general Windows ... The real problem here is that the emulator that eVC knows about is ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: sdk question
    ... with it via Platform Manager and eVC (PM is the piece that eVC uses, ... SURE THAT IT DOES NOT SAY ANYTHING ABOUT THE STANDARD SDK. ... Emulator, if your device SDK has an emulator for the device. ... Windows CE is not like desktop Windows. ...
    (microsoft.public.windowsce.embedded.vc)