Windows Mobile Application Development FAQ)

Q: What is Windows Mobile?

A: Windows Mobile is a Microsoft software platform for Pocket PC and smartphone. Windows Mobile extends familiar Windows desktops to personal devices.

Q: What is the difference between a Pocket PC and a smartphone?

A: Consider Pocket PC and smartphone.
Main usage features. Smartphone
It is mainly designed as a telephone device in terms of format and usage. It is fine-tuned and can be used to send and receive calls, and can also be used as a message processing device. Pocket PC
Designed mainly as a small PC, it is good for viewing and managing data and enhancing message processing. Some Pocket PCs
The device also has the telephone function. You should try to adjust your application based on the features of the target Windows Mobile DeviceProgram.

Q: What are the different versions of Pocket PC and smartphone (such as 2002 and 2003 )?

A: each new version of Windows Mobile is built on a wide range of existing development platforms available for developers, while maintaining a consistent core, in this way, applications can target various devices. Currently, there are three common Windows Mobile Software Versions:

• Windows Mobile 2002 software: the software that runs a device is sometimes called Pocket PC 2002 and smartphone 2002. New developer features include mapi and Connection Manager.

• Windows Mobile 2003 software: Version 2003
. NET Compact framework is added to the 2003-based device Rom. This allows developers
Write and host 2003 of devicesCodeApplication. Other new features include Configuration Manager, Bluetooth programmability, and SMS interception support.

• Windows Mobile 2003 second
Edition: Second Edition allows device manufacturers to use the main features of this version (for example
Horizontal, square, high-resolution screen, and qvga of smartphone
Screen support) for innovation. Its name reflects the consistency of the Development Platform, which has not changed for this version. All APIs that support the new screen direction and resolution are always part of the platform.

Q: How can I identify different software versions?

A: both the Pocket PC and Smartphone have an about panel in settings. Settings can be found from the Start menu of the two devices.

Based on the code, you can use the getversionex function to query the maximum and minimum OS versions and the exact internal version number of the software.

• Windows Mobile 2002-OS version: 3.0

• Windows Mobile 2003-OS version: 4.20

• Windows Mobile 2003 Second Edition-OS version: 4.21

Q: What should I do in my application to support Windows Mobile 2003 second edition enhancements (such as high resolution or landscape screens?

A: Windows Mobile 2003 second edition provides brand new screen orientation and resolutions, including horizontal, square, and VGA support for Pocket PCs and qvga support for smartphone. This version does not require a new SDK.

1. Read the best practices in the White Paper in the Windows Mobile 2003 second edition developer resources package.

2. Test your application by using the Pocket PC and smartphone Windows Mobile 2003 second edition simulators.

3. Make the application screen orientation and resolution independent, so that you can use a code base to target all hardware innovations on the Windows Mobile platform.

Download the new Windows Mobile developer resource package, including new and updated code samples and white papers.

Pocket PC development

Q: What tools can be used to develop Pocket PC 2003?

A: To build a local C ++ application for Pocket PC 2003, you need
Microsoft Embedded Visual C ++ 4.0, Microsoft Embedded Visual C ++ 4.0
Service Pack 3 and Pocket PC 2003 software development kit. You can download the Embedded Visual C ++ tool and
Pocket PC 2003 SDK. Windows Mobile 2003 second edition simulator package enables you
Test your application on the edition device. Note that the Pocket PC 2003 SDK does not support Microsoft embedded.
Visual Basic development. To build a Pocket PC 2003 hosting code application, you need Visual Studio. NET
2003 and Pocket PC 2003 SDK.

To build a Pocket PC mobile Web application, you can use the ASP. NET mobile control in Visual Studio. NET 2003.

Q: Can a Pocket PC 2002 application work on a Pocket PC 2003 device?

A: Pocket PC 2002 applications with well-functioning documentation APIs can run on the Pocket PC 2003 device without recompilation.

Q: Why does Pocket PC 2003 no longer support EVB development?

A: We will continue to support EVB on the Pocket PC 2003 device.
Run as an installable Ram component, so that the old EVB application can run on the new device, but leave Visual Basic
. Net, Visual C #. net, and Microsoft. NET Compact framework
More powerful and robust development experience, new EVB development for Pocket PC 2003 devices will not be supported.

According to customer feedback, the Pocket PC 2003 device will be included in the ROM
. NET Compact framework .. NET Compact framework is a complete. NET Framework.
Is a subset of smart devices. It is more specific to EVB than that provided by Pocket PC 2000 and Pocket PC 2002 devices.
The runtime is a more comprehensive and language-independent application engine.

Q: How do I migrate data from EVB to Visual Basic. Net?

A: It is not easy to migrate from EVB to Visual Basic. net, but the benefits of migration far exceed the cost:

• Richer data types: EVB only has 16-byte variant; Visual Basic. net uses. NET Framework generic type systems.

• Faster execution: EVB needs to be explained; Visual Basic. Net compiles JIT (Real-Time) into local code before execution

• Improved error handling: EVB only supports "on error" and Visual Basic. Net supports structured exception handling.

• Supported structure: EVB is not supported; Visual Basic. Net supports namespaces, classes, and structures.

• Object-oriented: EVB is procedural; Visual Basic. Net supports full OOP (Object-Oriented Programming)

• Top citizens: EVB always wants to catch up with MFC; Visual Basic. NET is the core. net

• Local XML support: not supported by EVB; Visual Basic. Net supports local XML and XML Web Services

• Improved data model: Ado. Net far exceeds adoce; it is still the best data model

• Safer and more reliable execution: EVB is a scripting language, and Visual Basic. Net is a hosted code.

• There are many more!

At the same time, there are a variety of resources (from porting experiments to technologyArticle) Helps developers perform this transition.
An example is a technical article describing how to migrate from EVB to Visual Basic. NET and its advantages: moving from embedded
Visual Basic to Visual Basic. net.

Q: What development tools do I use to compile a. NET Compact framework-based Pocket PC application?

A: Microsoft Visual Studio. NET 2003
Allows Visual Basic. Net or C # programmers to create Pocket PC 2000, Pocket PC 2002, and pocket
Managed code applications for PC 2003 devices (that is, applications that target the. NET public language runtime ). To develop Pocket PC 2000 and
Pocket PC 2002 device hosting code application, you can use the ready-to-use Visual Studio. NET
2003. During development, Visual Studio. NET 2003 will automatically
Install it in the ram of these devices .. NET Compact framework is already in the ROM of all the Pocket PC 2003 devices, and
Visual Studio. NET 2003 supports it through the Pocket PC 2003 SDK.

Q: What resources can be used for Windows Mobile 2003 second edition development?

Download the new Windows Mobile developer resource package, including the White Paper and new and updated code samples. This version does not require a new SDK.

You can use the new simulator package to test your application.

Embedded Visual C ++ 4.0 developers should download Embedded Visual C ++ 4.0 Service Pack 3.

Smartphone Development

Q: What tools can be used for smartphone 2002 development?

A: To start developing Microsoft smartphone 2002 applications, you need embedded Visual C ++ 3.0 and smartphone 2002 sdks. Both are available in Windows Mobile developer.

Q: When can I use. NET Compact framework for smartphone 2002?

A: The first version of. NET Compact framework focuses on successful
Pocket PC devices support smart device programming. Add the. NET Compact framework to
In Smartphone 2003. The. NET Compact framework for smartphone 2002 is not released
Version plan.

Q: Can MFC or ATL be used for smartphone 2002 development?

A: No. Smartphone 2002 does not support MFC and ATL development.

Q: Can I use embedded Visual Basic 3.0 to build a smartphone 2002 application?

A: No. It does not support EVB development with the smartphone 2002 as the target.

Q: What tools can be used for Microsoft smartphone 2003 programming?

A: There are two development options for Smartphone 2003, or
Service Pack 3 Embedded Visual C ++ 4.0 to develop local code, or use Visual Studio. NET
2003 develop managed code. You need to download the Smartphone 2003 SDK in both cases. Windows Mobile 2003 second
The edition simulator package allows you to test applications on a second edition device.

Embedded Visual C ++ 4.0 and Smartphone 2003 sdks can be obtained in Windows Mobile developer.

Q: Which version of. NET Compact framework can be used on Smartphone 2003?

A: Smartphone 2003 allows developers to use. net.
Compact Framework 1.0 Service Pack 1 is encoded .. NET Compact framework can be placed in
In the ROM of Smartphone 2003 .. NET Compact Framework 1.0 Service Pack 2 put in
In the ROM of Smartphone 2003 second edition.

Q: Can a smartphone 2002 application work on a smartphone 2003 device?

A: The smartphone 2002 application that uses the documented API and has good functionality can run on the Smartphone 2003 device without recompilation.

Q: What are the sample smartphone 2002 devices and Smartphone 2003 devices?

A: The original orange SPV and orange SPV E100 run
Windows Mobile 2002. The MPX200 on orange and at&t is based on Windows Mobile
Smartphone 2002. Run Windows Mobile 2003 in orange SPV e200.

Q: Can MFC or ATL be used for Smartphone 2003 Development?

A: MFC cannot be used in Smartphone 2003. You can use ATL 4.0 for Smartphone 2003 Development. For more information about ATL 4.0, see the SDK documentation.

Q: Where can I find more information about the smartphone application security model?

A: To help developers understand Windows Mobile-based
Smartphone application security model. We have created a White Paper. See

Http://msdn.microsoft.com/library/en-us/dnsmtphn2k3/html/smartphone_security.asp.

Q: What is the prompt mode?

A: OEMs or carriers can include the prompt mode in their smartphone application security policies to allow users to decide whether to install or run an application during installation or operation.

Q: Can I use embedded Visual Basic 3.0 to build a Smartphone 2003 application?

A: No. It does not support EVB development with the Smartphone 2003 as the target. If you want to use visual basic development skills, consider using Visual Basic. NET and target the. NET Compact framework.

Q: What resources can be used for Windows Mobile 2003 second edition development?

Download the new Windows Mobile developer resource package, including the White Paper and new and updated code samples.

You can use the new simulator package to test your application.

Embedded Visual C ++ 4.0 developers should download Service Pack 3 for Embedded Visual C ++ 4.0.

Mobile development tools

Q: What is Microsoft Embedded Visual tools 3.0?

A: Embedded Visual tools 3.0 is an integrated development environment.
(IDE), which is used by mobile developers to write software applications for 32-bit devices based on the Microsoft Windows CE operating system. Including the full version
Microsoft Embedded Visual C ++ 3.0, Microsoft Embedded Visual Basic
3.0 language, platform-specific sdks, remote tools, and documentation.

Q: What device platforms does Embedded Visual tools 3.0 support?

Answer: Embedded Visual tools 3.0-2002
Edition is attached to Pocket PC 2000, Pocket PC 2002, and smartphone 2002
SDK, and supports the development of custom Windows CE 3.0 devices.

Note: The Pocket PC 2002 SDK can be used with embedded
Visual Basic 3.0 and Embedded Visual C ++ 3.0 are used together, but the smartphone 2002 SDK
But only supported by embedded Visual C ++ 3.0.

Q: What is embedded Visual C ++ 4.0?

A: Embedded Visual C ++ 4.0
Is a powerful development tool for the next generation of Windows CE-based devices (including Pocket PC 2003 and smartphone
2003) Building a local code application can provide considerable benefits for enterprises. This independent integrated development environment (IDE) brings about a new level of Windows CE
Development efficiency, but it does not sacrifice flexibility, performance or control. To use the Embedded Visual C ++ tool to build a Pocket PC 2003 and
Smartphone 2003 application, you also need embedded Visual C ++ 4.0 Service Pack 3 and
Pocket PC 2003 and Smartphone 2003 sdks. Download the Embedded Visual C ++ 4.0 tool.

Q: Can I use embedded Visual C ++ 4.0 to develop a Pocket PC or smartphone application?

A: You can use embedded with Service Pack 2.
Visual c ++ 4.0 is used to develop Pocket PCs, including Windows Mobile 2003 second edition.
2003 and Smartphone 2003 applications. You can also use it to develop Pocket PC 2002 or smartphone 2002.
Application.

Q: Can I use the Windows CE standard SDK to develop a Pocket PC or smartphone application?

A: Windows CE SDK
Provides a general function subset so that the compiled applications can comply with the standard SDK, so that they can run in Windows CE. net based on custom display.
Platform. To build Pocket PC and smartphone smart device applications to take advantage of the rich set of device functions provided by these platforms, you need to use device-specific
SDK.

Q: What is the difference between embedded Visual tools 3.0 and Visual Studio. NET?

A: Embedded Visual tools 3.0
It is an independent development environment dedicated to mobile and embedded technology developers. For Pocket PC and smartphone, you can use embedded
Visual tools and appropriate platform sdks are used to build rich "Local Code" client applications. Visual Studio. NET is
The latest version of Microsoft's most popular desktop development tool. You can use Visual Studio. NET 2003 to build a. Net-based
Compact framework's Pocket PC smart client application. You can also use Visual Studio. NET and
ASP. NET mobile control builds browser-based applications targeting various devices (including devices in the Pocket PC and smartphone categories.