Windows CE - Where to start?
Norman Bullen
to be a lot of programmers over there, I hope you'll excuse my reposting
it here.
I've just purchased a WinCE device, primarily for the built-in features,
but, being a programmer, I can't resist the temptation to get into WinCE
programming. I've already got a couple of ideas for small applications
that will make my business life easier and might even be viable
shareware apps.
Before I go off the deep end, however, I'm trying to find out what I
need. It appears from my reading that I need two things:
1) the SDKs: a primary SDK as well as possibly several platform SDKs
2) a WinCE Tool Kit for either Visual C++ or Visual Basic
Apparently the SDKs can be downloaded from Microsoft and/or are included
in a WinCE book that I might buy.
However it looks like I need to buy the Took Kit. Before I do that, I'm
hoping to get some answers to the following questions:
1) Are the C++ Tool Kit compilers usable without Visual C++, or are they
"plug-ins" that can only be used as part of VC 6.0?
2) If VC 6.0 is required, which edition? Do I need Enterprise or
Professional Editions? Or will the Standard Edition work?
3) Which Edition of Visual Basic is required to work with the VB Tool
Kit?
4) Which development environment (VC++ or VB) likely to make smaller
apps to be loaded on the WinCE device? I guessing that a pure API C
program requires very little support beyond the native WinCE API whereas
a VB app probably carries along some VB DLLs. Or are those DLLs already
installed on the WinCE device?
TIA for any comments and insight from experienced WinCE programmers.
Norm
d.k. henderson
d.k. henderson
Jim M
>I've already posted this to the WinCE group, but since there don't seem
>to be a lot of programmers over there, I hope you'll excuse my reposting
>it here.
Check out "microsoft.public.win32.programmer.wince" for lurking CE
programmers.
>Before I go off the deep end, however, I'm trying to find out what I
>need. It appears from my reading that I need two things:
>
>1) the SDKs: a primary SDK as well as possibly several platform SDKs
>2) a WinCE Tool Kit for either Visual C++ or Visual Basic
>
>Apparently the SDKs can be downloaded from Microsoft and/or are included
>in a WinCE book that I might buy.
>
>However it looks like I need to buy the Took Kit. Before I do that, I'm
>hoping to get some answers to the following questions:
>1) Are the C++ Tool Kit compilers usable without Visual C++, or are they
>"plug-ins" that can only be used as part of VC 6.0?
The WinCE toolkit is a plug-in for VC++6. This will enable you to
build for CE2.0, CE2.01 and CE2.10. To build for CE 2.11, you will
need to download the extra bit that MS forgot to put on the Toolkit
CD, which includes a load of other chip-types for CE 2.11. This is a
hefty 76 meg download, and you will need the toolkit as well.
>2) If VC 6.0 is required, which edition? Do I need Enterprise or
>Professional Editions? Or will the Standard Edition work?
At least "VC++6 Professional Edition".
>3) Which Edition of Visual Basic is required to work with the VB Tool
>Kit?
Probably the Professional version too. Not too "up" on the VBside of
things.
>4) Which development environment (VC++ or VB) likely to make smaller
>apps to be loaded on the WinCE device? I guessing that a pure API C
>program requires very little support beyond the native WinCE API whereas
>a VB app probably carries along some VB DLLs. Or are those DLLs already
>installed on the WinCE device?
You've got it.
Pure API is the smallest.
MFC CE is the next biggest (non debug DLL's weighing in at about 400
K), but on _some_ of the CE devices, the MFC DLL is in ROM. But then,
it depends what version of MFC you are writing for.
I imagine VB would be hefty, but I wouldn't know, sorry :-(
>TIA for any comments and insight from experienced WinCE programmers.
>
>Norm
Hope this helps,
Jim M
--
@ Derbyshire