Clarification on OS and .NET CF compatibility is required

[Guest]

I want to know differences between various OS and tools which can be used to
develop application on them.

1) I want to know which of the following OS support .NET CF:
Pocket PC 2000
Pocket PC 2002
Pocket PC 2003
Win CE 3.0
Win CE 4.0
Win CE 4.1
Win CE 4.2

2) Say if I want to use any of the above OS what is the development
environment I
can use:
Which SDK is required?
Which eVT is compatible with which OS?
Which eVT code can be used in .NET framework?

Finally if I have a device which supports Pocket PC 2002 the to develop .NET
Framework Application what are the things which I require? In the sense Do I
need runtime for the device? Do I need a different SDK than the current one?
Currently I am using eVT 3.0 but can I use eVT 4.0

 

[Peter Foot [MVP]]

Answers inline:-

I want to know differences between various OS and tools which can be used
to
develop application on them.

1) I want to know which of the following OS support .NET CF:
Pocket PC 2000
Pocket PC 2002
Pocket PC 2003

Yes all versions of Pocket PC support NETCF v1.0. You may need to install
the Runtimes onto the device (although these are in ROM on all 2003 devices)

Win CE 3.0
Win CE 4.0

These versions of CE are not supported. Although Pocket PC 2000 and 2003 are
based on CE 3.0 no other CE 3.0 configurations are supported.

Win CE 4.1
Win CE 4.2

CE 4.1 and above support .NETCF however your platform requires certain
pre-requisite features so you will need to check with your platform
supplier.

2) Say if I want to use any of the above OS what is the development
environment I
can use:
Which SDK is required?
Which eVT is compatible with which OS?
Which eVT code can be used in .NET framework?

Development for .NETCF can be done with Visual Studio 2003 Professional or
above. Code can be written in VB.NET or C#. You cannot directly convert code
written in previous embedded Tools. There are tools available to help
migration from eVB. You can also make use of static C functions exposed from
dlls written with eVC++ using Platform Invoke

Finally if I have a device which supports Pocket PC 2002 the to develop
.NET
Framework Application what are the things which I require? In the sense Do
I
need runtime for the device? Do I need a different SDK than the current
one?
Currently I am using eVT 3.0 but can I use eVT 4.0

You need Visual Studio 2003 Professional. No further SDKs are required for
Pocket PC 2002 support - an emulator is included. The runtimes will be
deployed to the device when you deploy code from Visual Studio to the
device, you can also copy the cab files directly to the device and install
them. See the .NETCF section on MSDN for more details including the FAQ and
articles on some of the above topics:-
http://msdn.microsoft.com/mobility/netcf/

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups

 

[Guest]

Hi,
Like I had mentioned in my earlier, I have device which runs on Pocket PC
2002 and the vendor has provided me SDK for the device.
Now my question is to develop appilcation in .NET CF I just need Visual .NET
2003 pro and above?
How I am going to use the SDK in this case? Does vendor needs to update SDK
to support .NET CF

 

[Peter Foot [MVP]]

The vendor may have .NETCF supported APIs in which case you should find out
if they have an SDK for your device. If your SDK contains header files for
C++ development then it may be possible to use Platform Invoke to call them,
but that depends on the data types involved and whether the functions are
static C type functions or C++ classes.
So check with your vendor first if they have a .NETCF API for your device.
What device specific functionality are you wishing to make use of?

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups

 

[PeterB]

That would be best for you. If they provide a .NET SDK you can incorporate
it into VS very easy.

You can use a non managed SDK by calling dlls with Platform Invoke as Peter
Foot explained earlier, but you'd be best off with a full .NET SDK!

/ Peter