[Kris Kumar]

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppcgen/html/SymbianMigration.asp

"This article is for C++ developers who use Symbian OS and who have developed, or are developing, C++ applications for Symbian OS platforms, such as Series 60 or UIQ, and developers who want to implement their applications on the Windows Mobile operating system for Smartphones. When you first compare the Symbian OS application architecture with the architecture of a Windows Mobile application, they seem to have very little in common. On the Symbian OS, you build C++ graphical user interface (GUI) applications within an application framework by extending base classes that are provided as part of the platform, whereas eMbedded Visual C++ applications that are based on the Windows Mobile operating system are not so closely coupled to the operating system. Windows Mobile has no direct equivalents for common Symbian OS constructs such as two-phase construction or the cleanup stack, and Windows Mobile does not use a Symbian-style client-server model for accessing system resources, such as the file system or socket server."



Are you a developer for the Symbian platform? Wondering what it is like to port applications over to the Windows Mobile based Smartphones? The MSDN article written by Andy Wigley, is for the Symbian developers who want to understand the steps involved in migrating applications written for Symbian OS platforms, such as Series 60 and UIQ, to Windows Mobile–based Smartphones. :-)

[Kris Kumar]

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppcgen/html/SymbianMigration.asp

"This article is for C++ developers who use Symbian OS and who have developed, or are developing, C++ applications for Symbian OS platforms, such as Series 60 or UIQ, and developers who want to implement their applications on the Windows Mobile operating system for Smartphones. When you first compare the Symbian OS application architecture with the architecture of a Windows Mobile application, they seem to have very little in common. On the Symbian OS, you build C++ graphical user interface (GUI) applications within an application framework by extending base classes that are provided as part of the platform, whereas eMbedded Visual C++ applications that are based on the Windows Mobile operating system are not so closely coupled to the operating system. Windows Mobile has no direct equivalents for common Symbian OS constructs such as two-phase construction or the cleanup stack, and Windows Mobile does not use a Symbian-style client-server model for accessing system resources, such as the file system or socket server."



Are you a developer for the Symbian platform? Wondering what it is like to port applications over to the Windows Mobile based Smartphones? The MSDN article written by Andy Wigley, is for the Symbian developers who want to understand the steps involved in migrating applications written for Symbian OS platforms, such as Series 60 and UIQ, to Windows Mobile–based Smartphones. :-)