Migrating from WM5 to WM6

Hi.

I was asked to estimate how much time it will take to move a software from
an iPaq 2190 to an iPaq 114.

The iPaqs are almost the same but the 114 runs the wm6.

1) Is it fully compatible regarding software that was written to the wm5?

1.1) If not, what should be done in order to migrate it?

2) Any better BT programming support on the WM6?

3) Is the memory managment really gotten better and I'll be able to get all
my dll's in one piece into the memory? :-)


Thanks.


Empi

You should be able to migrate your app simply and it should work. After all
WM6 is still based on Win CE5.0 it's just the shell thats changed.

A couple of other things should make life easier for you. WM6 has CF 2.0 and
SQL CE 3.0 (SQL CE 2005) in ROM which makes deployment easier.

I don't *think* there are nay bluetooth changes. Of course since CF 2.0 we
can enjoy the SerialPort class.
--
Simon Hart
Visual Developer - Device Application Development MVP
http://simonrhart.blogspot.com


"Empi" wrote:

> Hi.
>
> I was asked to estimate how much time it will take to move a software from
> an iPaq 2190 to an iPaq 114.
>
> The iPaqs are almost the same but the 114 runs the wm6.
>
> 1) Is it fully compatible regarding software that was written to the wm5?
>
> 1.1) If not, what should be done in order to migrate it?
>
> 2) Any better BT programming support on the WM6?
>
> 3) Is the memory managment really gotten better and I'll be able to get all
> my dll's in one piece into the memory? :-)
>
>
> Thanks.
>
>
> Empi
>
>
>

Regarding 2)

..NETCF has no inherent Bluetooth support. If your device uses the Microsoft
Bluetooth stack you can use the shared source 32feet.NET library which
exposes a familiar Sockets programming model for managed code
(http://inthehand.com/content/32feet.aspx). Many iPaqs use the Broadcom
Bluetooth stack, the SDK is available for the broadcom stack but it is
native code (C++) only. As Simon pointed out in his response you can
manually configure a virtual COM port and then use the SerialPort class in
..NETCF 2.0 to send/receive data.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
www.peterfoot.net | www.inthehand.com
In The Hand Ltd - .NET Solutions for Mobility

"Empi" <mpeleg@softstart.co.il> wrote in message
news:OtKD1PXnIHA.3532@TK2MSFTNGP05.phx.gbl...
> Hi.
>
> I was asked to estimate how much time it will take to move a software from
> an iPaq 2190 to an iPaq 114.
>
> The iPaqs are almost the same but the 114 runs the wm6.
>
> 1) Is it fully compatible regarding software that was written to the wm5?
>
> 1.1) If not, what should be done in order to migrate it?
>
> 2) Any better BT programming support on the WM6?
>
> 3) Is the memory managment really gotten better and I'll be able to get
> all my dll's in one piece into the memory? :-)
>
>
> Thanks.
>
>
> Empi
>

Thank you very much.

Regarding the SerialPort, I'm afraid it is doing some bad things to the
system if I turn it off ("standby") while the port is open.
That's why I implemented my own "rs232" class that uses api's such as
readfile and writefile.

Thanks for the answers and best regards.


Empi


"Peter Foot" <feedback@nospam-inthehand.com> wrote in message
news:7FA1AA83-3493-4759-B683-37EF7A05E05E@microsoft.com...
> Regarding 2)
>
> .NETCF has no inherent Bluetooth support. If your device uses the
> Microsoft Bluetooth stack you can use the shared source 32feet.NET library
> which exposes a familiar Sockets programming model for managed code
> (http://inthehand.com/content/32feet.aspx). Many iPaqs use the Broadcom
> Bluetooth stack, the SDK is available for the broadcom stack but it is
> native code (C++) only. As Simon pointed out in his response you can
> manually configure a virtual COM port and then use the SerialPort class in
> .NETCF 2.0 to send/receive data.
>
> Peter
>
> --
> Peter Foot
> Microsoft Device Application Development MVP
> www.peterfoot.net | www.inthehand.com
> In The Hand Ltd - .NET Solutions for Mobility
>
> "Empi" <mpeleg@softstart.co.il> wrote in message
> news:OtKD1PXnIHA.3532@TK2MSFTNGP05.phx.gbl...
>> Hi.
>>
>> I was asked to estimate how much time it will take to move a software
>> from
>> an iPaq 2190 to an iPaq 114.
>>
>> The iPaqs are almost the same but the 114 runs the wm6.
>>
>> 1) Is it fully compatible regarding software that was written to the wm5?
>>
>> 1.1) If not, what should be done in order to migrate it?
>>
>> 2) Any better BT programming support on the WM6?
>>
>> 3) Is the memory managment really gotten better and I'll be able to get
>> all my dll's in one piece into the memory? :-)
>>
>>
>> Thanks.
>>
>>
>> Empi
>>
>