Re: Migrating from winCE5.0 to WinCE6.0
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Thu, 8 Feb 2007 09:49:02 -0500
1. In general, your apps should port nicely. I believe your main issues
will be porting between the two tools. If you use MFC, you may have some
trouble as some classes have been removed. VS2005 SP1 added a number of
them back in, you need to install that for app development.
2. The viewers were licensed from a third party in CE5, and have now been
dropped. You can get them directly from Westtek at http://www.westtek.com/.
3. In most cases, yes. The idea is that "well behaved" applications that
don't use undocumented tricks should work just fine.
4. Yes
5. Yes
6. Yes. CE5 did too...
The effort in moving from CE5 to CE6 is not app development. It is porting
your BSP (assuming you are an OEM) to the new OS. Drivers/OAL are the area
that will require the most work.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"Amit Golhani" <AmitGolhani@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2D8FAD57-24AF-43D1-BA09-017C413D9E68@xxxxxxxxxxxxxxxx
Hi,
We are planning to migrate from winCE5.0 to winCE6.0.
1. Will it require major change in application devloped in WinCE5.0 using
eVC++ or all the application will work in WinCE6.0 (VC++) without any
modification?
2. In winCE 6.0 ,is there any file viewer(for word,pdf,excel,image) or
removed from WinCE 6.0.If removed from WinCE 6.0 is there any option to
add
file viewer?
3. Application compiled & build in eVC++ will work on the image build in
WinCE6.0?
4. Will it support COM?
5. Will it support RAS?
6. Will it (winCE6.0) work on large disk more than 20GB ?
please help me to evaluate wince6.0.
Thanks in Advance.
Amit
.
- Prev by Date: Interaction with wince server(smartphone) through socket programming by other clients
- Next by Date: Re: Unable to get debug message which is in kernel
- Previous by thread: Interaction with wince server(smartphone) through socket programming by other clients
- Next by thread: WinCE6: FreePhysPage() - DEBUGCHK (pfi->pUseMap[ix]) failed
- Index(es):
Relevant Pages
|