Develop a Windows Mobile Application: FAQ

FAQs

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: Pocket PCAnd SmartphoneWhat is the difference between them?

A: consider the main features of Pocket PC and smartphone. 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 PC devices also have the telephone function. You should try
Use features of Windows Mobile devices to adjust your applications.

Q: Pocket PCAnd SmartphoneDifferent versions (for example
2002 , 2003 )?

A: Windows Mobile
Each new version of the software is built on a variety of existing development platforms available for developers, while maintaining a consistent core, so that the application can be oriented to a variety of devices. Currently, there are three common Windows
Mobile Software Version:

• 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: 2003 software version adds. NET Compact framework to a 2003-based device
  Rom. This allows developers to write managed code applications for devices based on Windows Mobile 2003. Other new features include Configuration Manager, Bluetooth programmability, and SMS
  Interception supported.

• Windows Mobile 2003 second edition: Second Edition allows device manufacturers to use the main features of this version (for example
  Horizontal, square, and high-resolution screens of the Pocket PC and qvga of the 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 set from the start
Menu.

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: to support Windows Mobile 2003 Second Edition
(For example, high resolution or landscape screen), what should I do in my application?

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

1. Read Windows
   Mobile 2003 second edition developer ResourcesBest practices in the whitepaper in the software package.

2. TestYour application, usePocket
   PCAndSmartphone
   Windows Mobile 2003 second edition simulator.

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

Download new
The Windows Mobile developer package contains new and updated code samples and white papers.

Pocket PCDevelopment

Q: What tools can be used Pocket PC 2003Development?

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 downloadEmbedded
Visual c ++ ToolAndPocket
VPC 2003 SDK. The Windows Mobile 2003 second edition simulator package enables you
Test your application on the second 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 needVisual Studio
. NET 2003AndPocket
VPC 2003 SDK.

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

Q: Pocket PC 2002The application can Pocket PC 2003
Does the device work?

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

Q: Why? Pocket PC 2003Not Supported EVBDevelopment?

A: On the Pocket PC 2003 device, we will continue to support the EVB runtime as an installable Ram component, such as the old EVB
The application can run on a new device, but it leaves Visual Basic. net, Visual C #. net, and Microsoft. NET.
The Compact framework provides a 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 include. NET Compact framework in the Rom .. NET Compact
The framework is a subset of the complete. NET Framework and is designed specifically for smart devices. It is a type
2002 a more comprehensive and language-independent application engine provided by the device that is specific to the EVB runtime.

Q: How EVBMigrate 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"; 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)

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

• XML support for local machines: EVB is not supported; Visual Basic. Net supports XML and XML Web Services for local machines.

• 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 technical articles) to help developers with this transition. An example is an overview of 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 . NET Compact frameworkOf Pocket PC
Application?

A: Microsoft Visual Studio. NET 2003 allows Visual Basic. Net or C # programmers to create pocket
Host code applications for PC 2000, Pocket PC 2002, and Pocket PC 2003 devices (that is, those with. net
Common Language Runtime Library as the target application ). To develop a hosted code application for Pocket PC 2000 and Pocket PC 2002 devices, you can use the out-of-the-box
Visual Studio. NET 2003. During development, Visual Studio. NET 2003 will automatically
Install the framework to the ram of these devices .. NET Compact framework is already in the ROM of all Pocket PC 2003 Devices
And Visual Studio. NET 2003 supports it through the Pocket PC 2003 SDK.

Q: What resources can be used? Windows Mobile 2003 Second EditionDevelopment?

Download new
The Windows Mobile developer package contains white papers 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.0Service Pack 3.

SmartphoneDevelopment

Q: What tools can be used Smartphone 2002Development?

A: To start developing Microsoft smartphone 2002 applications, you need embedded Visual C ++ 3.0 and
Smartphone 2002 SDK. Both of them can be found inWindows
Mobile developer.

Q: When can I . NET Compact frameworkUsed Smartphone 2002
?

A: The first version of. NET Compact framework focuses on providing smart device programming support for successful Pocket PC devices. Convert. NET Compact
Add the framework to Smartphone 2003. No. Net for smartphone 2002 is released
Plan the Compact Framework version.

Q: MFCOr ATLAvailable Smartphone 2002
Development?

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

Q: You can use Embedded Visual Basic 3.0To build Smartphone 2002
Application?

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

Q: What tools can be used? Microsoft smartphone 2003Programming?

A: There are two development options for Smartphone 2003, or embedded Visual C ++ with Service Pack 3
4.0 develop local code or develop managed code Through Visual Studio. NET 2003. Download in both casesSmartphone
2003 SDK. The Windows Mobile 2003 second edition simulator package enables you
Test the application on the second edition device.

Embedded Visual C ++ 4.0 and Smartphone 2003 sdks can be stored inWindows
Mobile developer.

Q: In Smartphone 2003Can be used on . NET Compact
FrameworkWhich version?

A: Smartphone 2003 allows developers to use. NET Compact Framework 1.0 Service Pack 1.
Encoding .. . NET Compact framework can be stored in the ROM of Smartphone 2003 .. NET Compact framework
1.0 Service Pack 2 is stored in the ROM of Smartphone 2003 second edition.

Q: Smartphone 2002Applications can To Smartphone 2003
Does the device work?

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 is an example? Smartphone 2002Device and Smartphone 2003
Device?

A: The original orange SPV and orange SPV E100 run Windows Mobile 2002. Orange and at&t
MPX200 is based on Windows Mobile 2002 smartphone. Orange SPV e200 running Windows
Mobile 2003.

Q: MFCOr ATLAvailable Smartphone 2003
Development?

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

Q: Where can I find more SmartphoneApplication Security Model Information?

A: To help developers understand the Windows Mobile-based smartphone application security model, we have created a White Paper. SeeHttp://msdn.microsoft.com/library/en-us/dnsmtphn2k3/html/smartphone_security.asp.

Q: What is the prompt mode?

A: The OEM or carrier can include the prompt mode in their smartphone
In the Application Security Policy, you can decide whether to install or run an application during installation or running.

Q: You can use Embedded Visual Basic 3.0Laijian Create
Smartphone 2003Application?

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 with. NET Compact framework as the target.

Q: What resources can be used? Windows Mobile 2003 Second EditionDevelopment?

Download new
The Windows Mobile developer package contains white papers 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
Embedded Visual C ++ 4.0 Service Pack 3.

Mobile development tools

Q: What is Microsoft Embedded Visual tools 3.0 ?

A: Embedded Visual tools 3.0 is an integrated development environment (IDE). mobile developers use
Write software applications for 32-bit devices in the operating system. Including the full version of Microsoft Embedded Visual C ++ 3.0 language, Microsoft
Embedded Visual Basic 3.0 language, platform-specific SDK, remote tools and documentation.

Q: Embedded Visual tools 3.0What device platforms are supported?

A:Embedded
Visual tools 3.0-2002 EditionAttached to Pocket PC 2000, Pocket PC 2002, and
Smartphone 2002 SDK, and supports the development of custom Windows CE 3.0 devices.
Note:Pocket PC 2002
The SDK can be used with Embedded Visual Basic 3.0 and Embedded Visual C ++ 3.0, but smartphone
The 2002 SDK is 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. 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. Use the Embedded Visual C ++ tool to build Pocket PC 2003 and smartphone
2003 applications, you also need embedded Visual C ++ 4.0 Service Pack 3 and Pocket PC 2003 and
Smartphone 2003 SDK. DownloadEmbedded
Visual c ++ 4.0Tool.

Q: I can use Embedded Visual C ++ 4.0Development Pocket PC
Or SmartphoneApplication?

A: You can use embedded Visual C ++ 4.0 with Service Pack 2 to develop Windows Mobile 2003
Pocket PC 2003 and Smartphone 2003 applications, including second edition. You can also use it to develop Pocket PC 2002
Or a smartphone 2002 application.

Q: I can use Windows CE standard SDKDevelopment Pocket PC
Or SmartphoneApplication?

A: The Windows ce sdk provides a general function subset so that the compiled applications can comply with the standard SDK to run in a custom display-based
Windows CE. NET platform. To build a Pocket PC and smartphone
Smart device applications use device-specific sdks to take advantage of the rich device feature sets provided by these platforms.

Q: Embedded Visual tools 3.0And Visual Studio. NET
What is the difference between them?

A: Embedded Visual tools 3.0 is an independent development environment dedicated to mobile and embedded technology developers. For Pocket PCs and
Smartphone, you can use embedded Visual tools and the appropriate platform SDK to build a wide range of "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 a variety of devices, including devices in the Pocket PC and smartphone categories.

Q: Why not Embedded Visual C ++Integrated Visual Studio. NET
Medium?

A: based on customer feedback, our initial work mainly focused on enabling Visual Basic. NET developers to program devices more easily. However, using the local code (C ++)
The function of creating a device application will be integrated into the next version of Visual Studio.

Q: What is . NET Compact framework ?

A:. NET Compact framework is a subset of. NET Framework. It is designed to run on devices with limited resources to host code and XML
Web services are supported .. NET Compact framework greatly reduces the development cost of applications and services written and run on Pocket PC devices. Because
. NET Compact framework is a subset of. NET Framework used by developers to write desktop and server applications, so they already have the ability to write
All tips required for Pocket PC and Smartphone 2003 device applications.

Q: Use . NET Compact frameworkWhat are the main benefits?

A: One of the biggest obstacles to writing device applications is that most devices require developers to understand different APIs and use different programming tools (compared with desktop applications ). Because. net
The. NET Framework programming model used by Compact framework and Visual Studio. NET
Development tools are the same as those used by developers on desktops and servers. Therefore, they can greatly reduce the cost of developing Device Applications and improve the efficiency of developers. These benefits allow enterprises to use smart devices in new ways to improve their business .. Net
Compact framework is also the only mobile development platform with local support for XML Web Services.

Q: What devices can run? . NET Compact framework ?

A:. NET Compact Framework 1.0 can be used as a Pocket PC 2000 and Pocket PC 2002 device (including phone
Edition), and can be stored in the ROM of Pocket PC 2003. Smartphone 2003 devices include. NET Compact
Framework 1.0 Service Pack 1. All Windows Mobile 2003 second edition devices include. net
Compact Framework 1.0 Service Pack 2.

Q: When can I use it? . NET Compact framework ?

A: Version 1.0 of. NET Compact framework can be used as Visual Studio. NET 2003.
Use part of the version. For more information, seeDevice
Development.

Q: . NET Compact frameworkAll . Net
Language?

A: Initially,. NET Compact framework can run Visual C # and Visual Basic. As long as other. NET languages comply with. net
A subset of the Common Language Runtime libraries supported by Compact framework can be run.

Q: . NET Compact frameworkApplications and Embedded Visual C ++
Is the application execution the same?

A: In most cases, applications written with Embedded Visual C ++ run faster than those written with Visual Basic. Net or Visual C #
Applications written in. NET are fast. However, for application computing intensive parts, developers will see their visual basic. NET applications than their embedded
Visual Basic applications have been substantially improved.

Q: . NET Compact frameworkAnd ASP. NET
What are the differences between mobile controls?

A: There are two different methods to program devices. One way is to place applications on smart devices. Another method is to place the code on the server and display the user interface in a browser .. Net
Compact framework supports the former, while ASP. NET mobile controls (formerly known as Microsoft mobile Internet Toolkit) support the latter.

Use the code on the device to build a mobile application so that the application has no Internet
You can continue to work when the connection is established. Applications running directly on devices also support richer user interfaces and the possibility of integration with available assets on the operating system (such as multimedia and other applications. Available
. NET Compact framework uses efficient models to build smart device applications.

Building a mobile app with code on the server also has its advantages. When you must use the Internet
This architecture is useful when supporting various mobile devices. These applications are not restricted by resources because they run on the same server as desktop Web applications. In Visual Studio
ASP. NET mobile controls can be used in. Net to write these applications.

Technical and market support

Q: How can I obtain technical support?

A: There are many technical support options, from free newsgroups to paid special support. For more information about these options, seeWindows
Mobile support.

Q: What is Mobile2marketProgram?

A: Microsoft mobile2market
It is a comprehensive program designed to enable developers and independent software vendors to increase revenue through the mobile operator relationship, while also expanding the scope of customers and reducing the time to enter the market. Mobile2market
The process consists of steps that include the application logo authentication and is included in the Microsoft application directory. AccessWww.microsoft.com/windowsmobile/mobile2market
For more information.

Q: What is the difference between application logo authentication and application signature?

A: Application logo authentication is the process of designing and building applications to comply with a set of best practices design guidelines. By enabling independent software vendors (ISVs)
Applications that are recognized by the logo can make their applications stand out in the market, greatly benefiting and ensuring the satisfaction of end users. To view the Pocket PC 2002 and
For more information about the logo authentication guidelines for smartphone 2002, see Windows
Mobile participant now.

Application signature applies to smartphone
2002, and refers to a device security concept. Specifically, the application signature refers to the process of digital signature (authentication and Authentication) for the application, so that it can be deployed to the actual
And run it on the smartphone 2002 device. The application signature must be set by the mobile operator and the specific smartphone device provided by the mobile phone.

Microsoft mobile2market
A program provides a framework that helps developers bring their applications to market in an effective way and describes the application signing, logo authentication, and sales processes. For more information, seeWindows
Mobile participant now.

Q: All SmartphoneDo I need to pass the logo authentication before the application is actually deployed to the device?

A: No. Application logo authentication is not required for developing apps on a Pocket PC or smartphone. However, independent software vendors (ISVs)
Through this process, their applications can be differentiated in the market, greatly benefiting and ensuring the satisfaction of end users. Another benefit of getting logo certification is that it can be included in Microsoft
In the application directory, it allows isV to obtain a wide range of customers. To view the specific logo certification instructors for Pocket PC 2002 and smartphone 2002, see
Windows
Mobile participant now.

Q: All SmartphoneDo applications require digital signatures before they can be actually deployed to a device?

A: No. The application signature must be set by the mobile operator and the specific smartphone device provided by the mobile phone. Microsoft mobile2market
Programs provide a framework to help developers bring their applications to market in an effective way and describe the process of application signatures, logo authentication, and sales. For more information, see Windows
Mobile participant now.