What's New in Windows Mobile 2003 Second Edition

Article
08/29/2006

This section describes the new features and major changes introduced for Microsoft Windows Mobile 2003-based Smartphones. For more information, see What's New for Developers in Windows Mobile 2003 Second Edition Software.

Development Environment

Microsoft .NET Compact Framework is included in ROM on all Windows Mobile-based devices. The .NET Compact Framework allows managed code applications to run on Windows Mobile 2003 devices.

For more information, see Microsoft .NET Compact Framework on MSDN.
Applications for Windows Mobile 2003 Smartphones can be written in C# or Microsoft Visual Basic .NET. You can now write managed code applications for Smartphones that can be developed through Microsoft Visual Studio .NET 2003 Smart Device Extensions.

For more information, see Smart Device Programmability on MSDN.

Device Emulator

The new emulator replicates a storage card by mapping a drive on the host desktop computer.
Emulator supports the Game API (GAPI) for game developers.
Emulator supports synchronizing over Ethernet without requiring the use of a serial port. For more information, see How to: Use ActiveSync over Virtual Switch.

Device ** Management

WAP Push Router extensibility allows for custom processing of WAP push messages. Applications can intercept different types of WAP push messages and reroute them to different push clients for custom handling through the PushRouter client functions declared in pushclient.h.

Security

Windows Mobile 2003 software for Smartphones offers users an optional security prompt, enabling them to allow or disallow installation or execution of unsigned applications.
Mobile2Market security certificates for Windows Mobile 2003 Smartphones are now included by default in ROM.
Mobile devices can now use Layer Two Tunneling Protocol (L2TP) with Internet Protocol security (IPSec) for making virtual private network (VPN) connections across public networks. This functionality is supported through the CM_VPNEntries Configuration Service Provider.

Web Development

Microsoft Pocket Internet Explorer has been updated to support the following:
- HTML 4.01
- Extensible HTML (XHTML)
- Cascading style sheets
- Microsoft JScript version 5.5
- Enhanced scripting and Document Object Model support
- Wireless Markup Language (WML) 2.0 (XHTML + WML 1.x)
- Internet Protocol version 6 (IPv6) in IPv4/IPv6 mixed-mode environments
- New extensible imaging library
For more information, see Designing Web Sites for Mobile Devices.

Shell

Home Screen functionality is updated for Windows Mobile 2003 Smartphones. To exend customization options the Home Screen plug-in infrastructure supports a new function, SHOnPluginDataChange, and a new interface, IHomePluginEnvironment2.

Messaging

Incoming SMS messages can be intercepted. Developers can use the IMailRuleClient interface to perform customized filtering rules on incoming messages and handle them as appropriate within their applications.
More e-mail services are configurable through Configuration Manager. The Email2 Configuration Service Provider enables the configuration of Internet Protocol e-mail services, such as Internet Message Access Protocol 4 (IMAP4) and Post Office Protocol 3 (POP3), using the device's Configuration Manager infrastructure.
Messaging Custom Read or Compose forms can be registered. The IMessageFormEx and IFormProviderEx interfaces allow developers to register a custom set of forms that match their application needs and that can be used to construct Enhanced Messaging Service (EMS) or Multimedia Messaging Service (MMS) clients.

Networking

IPv6 is supported. Most Windows Mobile-based Smartphone APIs and components now support IPv6-style addressing. IDccManSink2 is the new sink interface that supports IPv6 and is used to notify client applications about device connections.
Bluetooth functionality is more controllable. The BthGetMode and BthSetMode functions enable you to query the current state of the Bluetooth control panel and to modify its state.
Applications can be shut down and then awakened when a WAP packet arrives over SMS. For more information, see WAP Wakeup.

Important Changes

Development for Windows Mobile 2003-based Smartphones is supported only for eMbedded Visual C++ 4.0 with Service Pack 2 installed. Previous versions of eMbedded Visual C++ are not supported for development, deployment, and debugging of Windows Mobile-based Smartphone applications.
eMbedded Visual C++ ADOCE development is not supported on Windows Mobile 2003 software for Smartphones. If you want to use ActiveX® Data Objects (ADO) in your application, you must use managed code and ADO.NET.
All new COM objects, including ActiveX controls, must be free-threaded to optimize their performance. Previously developed COM objects continue to run correctly, regardless of their threading model, because the operating system performs run-time checks to help ensure that the correct threading model is used for code that was compiled for previous versions of the operating system.
New eMbedded Visual C++ (version 4.2) emulator cannot run side-by-side with previous versions. It also cannot run side-by-side with the emulators provided with Visual Studio .NET 2003 Smart Device Extensions. However, you can run multiple instances of the new emulator simultaneously.
Persistent storage folder renamed for Windows Mobile 2003 Smartphones. Windows Mobile 2002 Smartphones used the IPSM folder for persistent storage. The new name for this folder is Storage.
The following MAPI string constants are no longer supported:
- kszCapAmountToFetch
- kszCapAttachAmount
- kszCapAgeFilter
- kszCapSMTPAuthenticate
- kszCapMoveToTrash

Share via