Windows Mobile 6 Overview
Page 1 of 1
Windows Mobile 5/6 development is typically usually done using the Visual Studio 2005/2008 IDEs (integrated development environments). Since the Visual Studio IDE is extremely mature and used by millions of developers throughout the world, it is a relatively easy platform with which to begin mobile application development.
In addition to C/C++ development for Windows Mobile devices, another popular option is to develop applications for the .NET Compact Framework. The .NET CF is a version of the .NET Framework ported to operate under the constraints of Windows CE, Pocket PC, Smartphone and Windows Mobile operating systems. The .NET CF consists of a runtime system similar to the .NET Compact Framework, as well as the supporting class libraries and tools required to utilize the runtime. In this regard it is very similar to Java. Unlike Java, however, it is designed to be language agnostic and simply specifies the CIL (common intermediate language) instructions. Therefore all of the .NET supported languages, C#, VB.NET, J#, and many others, compile to the same CIL and can be executed by the .NET CF runtime.
Windows Mobile 6 Standard Overview
Unlike a Pocket PC or Pocket PC Phone, a Smartphone has phone capabilities and comes with a smaller set of applications. Smartphones also have smaller keypads and screens designed for quick, one-handed access.
Windows Mobile 6 Professional Overview
Windows Mobile 6, the latest version of the Microsoft Windows Mobile platform, puts Microsoft Office in users' pockets to help people stay productive wherever they go.
Windows Mobile Security Policies
Developers need to be aware of the Windows Mobile security policies on AT&T devices. On
two-tier devices, the apps and install packages should be signed and designed to run with
normal permissions (not privileged). Applications on a two tier device typically run under the
USER_AUTH role. The consequence of running under this role is that install packages and running
apps have a small set of limitations to contend with:
- They cannot read from protected areas of the registry
- They cannot read contents of files marked with the 'System' attribute.
- They cannot write to protected areas of the registry, to system files, or access files in the \Windows\System directory.
The "protected" areas of the registry include:
HKEY_LOCAL_MACHINE\Comm
HKEY_LOCAL_MACHINE\Drivers
HKEY_LOCAL_MACHINE\HARDWARE
HKEY_LOCAL_MACHINE\SYSTEM
HKEY_LOCAL_MACHINE\Init
HKEY_LOCAL_MACHINE\WDMDrivers
HKEY_LOCAL_MACHINE\Services
For more information on protected Registry Keys & Values, see the Microsoft
developer documentation. For more information on the security differences between single
tier & two-dier devices, please see http://msdn.microsoft.com/en-us/library/bb416353.aspx
Windows Mobile 5 and 6 C/C++ Libraries:
|
Library |
Purpose |
URL |
|
C/C++ Connection Manager |
For devices to automatically determine and create best connection based on hardware and user settings. |
|
|
Cell Core |
SMS, WAP, SIM and radio interface management. |
|
|
VoIP Services |
For applications to place and receive SIP calls. |
|
|
Wireless Networking APIs |
For Wi-Fi, IR, and Bluetooth communications. |
|
|
Remote Access Services |
Creation of VPN and PPP connections. |
|
|
Remote API 2 |
For desktop applications to perform operations on a Windows Mobile device. |
|
|
Networking Core |
APIs for direct use of Windows sockets, Berkeley sockets. |
|
|
Security |
For storing certificates and performing cryptographic functions. |
|
|
Installation |
For create a delivery CAB file that contains all application resources and binaries. VS 2005/2008 have built-in wizards to automatically create an installer for you. |
Mobile Application Development Quick Start Guide
Windows Mobile Developer Resource Kit on MSDN
Page 1 of 1
Add in your thoughts or see what others are saying: Go to the devCentral Web Boards
