Windows Mobile Development FAQ
Compilation: Liu Tiefeng
[Abstract] This article provides an answered question for Pocket PC and Smartphone developers or common issues raised by this interester.
common problem
Q: What is Windows Mobile?
A: Window Mobile is a Microsoft's Pocket PC and SMARTphone software platform. Windows Mobile extends the familiar Windows desktop system to your personal handheld devices.
Q: What is the difference between Pocket PC and SmartPhone?
A: We distinguish the Pocket PC and Smartphone based on the main use use. Smartphone is mainly designed as telephone devices in shape and function. It is ideal for calling and as an information management device. The Pocket PC is mainly designed to make it easy to view, manage data, and enhance small personal computers for information management. Some Pocket PC devices will also have a phone function. You can choose your application based on your different purposes of your Windows Mobile device.
Q: What is the difference between Pocket PC and SMARTPHONE, such as 2002 and 2003?
A: Each new Windows Mobile Software version is built on the original powerful development platform. At the same time, for developers, each new Windows Mobile Software has maintained the original core consistency to better compatibility. There is now mainly the following three Windows Mobile Software versions:
Windows Mobile 2002 Software: This software is mainly running on devices called Pocket PC 2002 and Smartphone 2002. It includes new features of MAPI and Connection Manager. Windows Mobile 2003 Software: This software version is attached to the ROM in the ROM based on the 2003-based device. Net CF. This feature allows developers to write managed code for Windows Mobile 2003-based devices. It also includes configuration management (Configuration Manager), supports Bluetooth programming, and new features that support SMS listening. The second edition of Windows Mobile 2003: This version provides a support screen horizontal reading mode (LANDSCAPE), providing high-resolution screen support for Pocket PC, and Square screen support, QVGA screens provided by SmartPhone. All names on all development platforms in this release have not made any changes, all APIs that support the new screen direction and resolution have become part of the platform.
Q: How do I identify different software versions?
A: Whether it is a Pocket PC or Smartphone has the "Set" panel. "Settings" can be found through the "Start" menu in both devices.
In programmed code, you can use the getVersionEx method to get the specific compilation of the operating system's primary, secondary number, and software. details as follows:
Windows Mobile 2002-OS Version: 3.0 Windows Mobile 2003-OS Version: 4.20 Windows Mobile 2003 Second Edition - OS Version: 4.21
Pocket PC development
Q: What tools can I support Pocket PC 2003 development?
A: If you use C for the Pocket PC 2003 development program, you will need to use Microsoft Embedded Visual C 4.0, Microsoft Embedded Visual C 4.0 Service Pack 3, and Pocket PC 2003 SDK. You can use the Second Edition of the Windows Mobile 2003 to test your programs on the second edition of the second edition.
Please note: Microsoft Embedded Visual Basic development is not supported in Pocket PC 2003 SDK. You will need to use the Visual Studion.Net 2003 and Pocket PC 2003 SDK to compile the program written by the Managed Code.
Q: Is the application on Pocket PC 2002 applied to Pocket PC 2003?
A: In general, using APIs developed in the documentation can work properly on Pocket PC 2002, you can run directly on Pocket PC 2003 without recompilation.
Q: Why does Pocket PC 2003 no longer provide support for EVB development environment?
A: We will always support the EVB operation on the Pocket PC 2003 device to support EVB operation, so the old version of the EVB program can also run on the new device. But we no longer provide new EVB development environments for Pocket PC 2003 devices, as we offer more powerful Visual Basic .NET, Visual C # .NET, and Microsoft.Net Compact Framework.
According to the feedback of users, the Pocket PC 2003 device will include .NET CF in the ROM. .NET CF is a subset of the full version of the .NET Framework, which is designed for smart devices development. It is not just similar to the EVB running environment provided in Pocket PC 2000 and Pocket PC 2002, which is also a complete language neutral program engine.
Q: How to migrate from Visual Basic .NET from EVB?
A: Although it is not easy to migrate from the EVB to Visual Basic .Net, you are absolutely worth doing.
More abundant data types; EVB only provides 16-bit Variant; Visual Basic NET can use all the basic data types in the .NET Framework. Faster execution speed: EVB is explained; Visual Basic .NET compiles the local code before execution through Just-in-Time. Better error handling mechanism: EVB only supports "on error"; Visual Basic .NET supports structured error handling. Provide Structure Support: EVB has no structure concept; Visual Basic .NET supports namespace (Classes), Classes, and Structures. Support for face-to-object: EVB is based on process; Visual Basic .NET fully supports better features of OOP (Object-orientated Programming): EVB only supports MFC; Visual Basic .NET is pure .NET and later XML support : EVB does not support XML; Visual Basic.NET supports XML and XML Web Services. Better data model: As our best data model, ADO.NET far exceeds Adoce. More secure, reliable execution: EVB is a scripting language; Visual Basic .NET is managed code. Similarly, from the example to the technical article, we have a variety of resource assistance developers to complete this transformation.
Q: What development tools can be used if you need to develop .NET CF-based programs for Pocket PC?
A: Microsoft Visual Studio .NET 2003 allows Visual Basic .NET or C # developers to write hosting code for Pocket PC 2000, Pocket PC 2002, Pocket PC 2003, etc., that is, these programs will be in .NET CLR Run down). There is no doubt that you can use Visual Studio .NET 2003 to develop managed code programs for Pocket PC 2000 and Pocket PC 2002. Visual Studio .NET 2003 automatically installs .NET CF on the RAM of these devices in the development. The .NET CF already exists in the ROM of Pocket PC 2003, and also supports Visual Studio .NET 2003 via Pocket PC 2003 SDK.
Q: What related resources are developing about the second edition of Windows Mobile 2003?
A: Download the new Windows Mobile 2003 Second EDTION Developer Resources Kit, which includes the latest and updated code examples and white paper. And this version does not require new SDK. You can test your program by using the new simulator toolkit. Embedded Visual C 4.0 developers should first download Embedded Visual C 4.0 Service Pack 3
Smartphone development
Q: What tools can I support SmartPhone 2002 development?
A: You can use Embedded Visual C 3.0 and Smartphone 2002 SDK to develop programs for Microsoft Smartphone 2002. These software can be obtained from the MSDN website. Q: When will there be a .NET CF that supports SmartPhone 2002 development?
A: The first version of the .NET Compact Framework is mainly developed to better support more successful Pocket PC related smart devices. We will increase the .NET CF in the SMARTPHONE's SMARTPHONE 2003 version. We have not planned to release the .NET CF supporting the Smartphone 2002.
Q: Is there a MFC or ATL that supports SmartPhone 2002 development?
A: No, MFC or ATL does not support smartphone 2002.
Q: Can I use Embedded Visual Basic 3.0 for SmartPhone 2002 development programs?
A: No. There is no EVB development environment for SmartPhone 2002.
Q: What tools can I support Microsoft SmartPhone 2003 programming?
A: With the release of SmartPhone 2003, you will have two development tools to choose from: using Embedded Visual C 4.0 with Server Pack 3 (using local code) or use Visual Studio .NET 2003 (using managed code). Anyway, you must download SmartPhone 2003 SDK. At the same time, the second edition of the Windows Mobile 2003 will allow you to simulate the test program on the second edition device.
These software can be obtained from the MSDN website.
Q: Which version of .NET CF can be used on SMARTPHONE 2003?
A: Smartphone 2003 allows developers to develop programs using .NET Compact Framework 1.0 Service Pack 1. .NET Compact Framework will be included in the ROM of Smartphone 2003. At the same time .NET Compact Framework 1.0 Service Pack 2 will exist in the SMARTPHONE 2003 second edition.
Q: Is the application on SmartPhone 2002 applied to SMARTPHONE 2003 related devices?
A: In general, using the API that represents the API indicated in the documentation can run properly on SmartPhone 2002, you can run directly on Smartphone 2003 without recompilation.
Q: What are the typical SMARTPHONE 2002 and SmartPhone 2003-based devices?
A: The initial Orange SPV and Orange SPV E100 are running over Windows Mobile 2002. The MPX200 is also based on Orange, AT & T is also constructed on SmpartPhone based on Windows Mobile 2002. Orange SPV E200 is running over Windows Mobile 2003.
Q: Is there a MFC or ATL that supports SmartPhone 2003 development?
A: The MFC does not support Smartphone 2003. You can use ATL 4.0 to develop for SmartPhone 2003. Check the SDK documentation to get more information about ATL 4.0.
Q: Where can I get more information about the SmartPhone application security model?
A: In order to facilitate developers to understand the Internet-based application security model based on Windows Mobile, we created related white paper. Specifically, you can refer to: http://msdn.microsoft.com/library/en-us/dnsmtphn2k3/html/smartphone_security.asp. Q: What is the command line mode?
A: OEM or operator can provide command line mode in the program. You can provide command line modes to provide command line mode by setting their SMARTPHONE application security policies.
Q: Can Embedded Visual Basic 3.0 can develop a SMARTPHONE 2003 development program?
A: No. There is no SMARTPHONE EVB development environment. If you want to use your Visual Basic's development skills, you can consider using Visual Basic .NET and .NET CF.
Q: What related resources are developing about the second edition of Windows Mobile 2003?
A: Download the new Windows Mobile 2003 Second EDTION Developer Resources Kit, which includes the latest and updated code examples and white paper. And this version does not require new SDK. You can test your program by using the new simulator toolkit. Embedded Visual C 4.0 developers should first download Embedded Visual C 4.0 Service Pack 3.
Mobile development tool
Q: What is Microsoft Embedded Visual Tools 3.0?
A: Embedded Visual Tools 3.0 is an integrated development tool. The development tool is primarily based on the development tools provided by the 32-bit device mobile application using the Microsoft Windows CE operating system. The full version of the development environment includes Microsoft Embedded Visual C 3.0, Microsoft Embedded Visual Basic 3.0, proprietary platform SDK, remote tools, and documentation.
Q: What equipment platforms supported by EMBEDDED VISUAL TOOLS 3.0?
A: Embedded Visual Tools 3.0 - 2002 Edition and SDK mainly supports Pocket PC 2000, Pocket PC 2002, Smartphone 2002, and other Windows CE 3.0-based devices.
Please note: Pocket PC 2002 SDK can use Embedded Visual Basic 3.0 or Embedded Visual C 3.0, regardless of whether SMARTPHONE 2002 SDK only supports Embedded Visual C 3.0.
Q: What is EMBEDDED VISUAL C 4.0?
A: Embedded Visual C 4.0 is a powerful development tool. It provides the greatest convenience for developing a new Windows CE device, including Pocket PC 2003, and Smartphone 2003, using the local code. This independent integrated development tool has brought higher levels of productivity for Windows CE procedures, while the flexibility, performance, and control of development have not lost. If you use the Embedded Visual C tool to develop for Pocket PC 2003 or SmartPhone 2003, you also need to download Embedded Visual C 4.0. Service Pack 3, Pocket PC 2003 SDK and Smartphone 2003 SDK. Q: Can Embedded Visual C 4.0 are Pocket PC or SmartPhone development programs?
A: You can use the Embedded Visual C 4.0 plus Service Pack 2 to develop applications for Pocket PC 2003 and the Smartphone 2003, including the second edition of Windows Mobile 2003. But it cannot be used for the development of Pocket PC 2002 and Smartphone 2002.
Q: Can you use the Windows CE Standard SDK for the Pocket PC or SmartPhone Developer?
A: The Windows CE SDK provides a set of characteristics of the public subset of features. These subsets can allow procedures to be developed in accordance with standard SDK to run on a Windows CE .NET platform. For better Pocket PC and smart device development procedures such as SmartPhone, it is recommended to use a proprietary device SDK for providing more features.
Q: What is the difference between Embedded Visual Tools 3.0 and Visual Studio.net?
A: Embedded Visual Tools 3.0 is an independent development environment. It mainly facing moving or embedded developers. For Pocket PCs and SmartPhone, you can use the Embedded Visual tool to add a powerful local code (Native Code) client program using the Embedded Visual tool. Use Visual Studio .NET 2003 to construct a Pocket PC smart client program based on .NET Compact Framework. It also uses Visual Studio .NET and ASP.NET mobile development controls to develop browser-based programs, which can support more devices, including devices such as Pocket PC and Smartphone.
Q: Why didn't I integrate Embedded Visual C 4.0 in Visual Studion.net?
A: According to user feedback, our initial efforts are concentrated on how to make Visual Basic .NET developers can more convenient development programs. However, we will integrate the ability to develop mobile device programs in the next version of Visual Studio.
Q: What is .NET Compact Framework (Abbreviation .NET CF)?
A: .NET Compact Framework is a subset of .NET Framework. Its main target needle is designed for resource limited equipment, providing support for managed code and XML Web Services. .NET Compact Framework has greatly introduced the number of programs that developers who develop devices that run in similar Pocket PCs. Because .NET Compact Framework is a subset of .NET Framework, so if developers have experience in developing desktops or server applications, they can also apply corresponding techniques to Pocket PC and Smartphone 2003 related device development procedures. Q: What is the biggest advantage of using .NET CF?
A: The biggest obstacle for different equipment development processes is that most devices require developers to learn more than APIs and programming tools than developing desktop programs. Because .NET CF uses the same programming model with .NET Framework and the same development tools as developing desktop or server programs, it greatly improves the developer's productivity. Conversely, it is also possible to improve the business volume for the promotion of the company's use of smart equipment to open up new ways. Similarly, .NET CF is also the only mobile development platform for XML Web Services supporting local code.
Q: What devices can be run on .NET CF?
A: .NET Compact Framework can be installed in the RAM of Pocket PC 2000 or Pocket PC 2002 related devices (including smartphone versions). At the same time, in the ROM of the Pocket PC 2003 related equipment, the .NET CF is included. SMARTPHONE 2003 devices and include .NET CF 1.0 and Server Pack 1. All .NET CF 1.0 Server Pack 2 is included in all Windows Mobile 2003 second editions.
Q: When can I use when I can use .NET CF?
A: The version of .NET CF 1.0 has been part of Visual Studio .NET 2003.
Q: Can all .NET languages support on .NET CF?
A: The initial .NET CF can support Visual C # and Visual Basic. As long as the CLR language supported by the .NET CF is used, other languages can also be run.
Q: Will .NET CF will be as good as Embedded Visual C ?
A: In most cases, the program developed using the Embedded Visual C will run speed than the program developed using Visual Basic .NET or Visual C # .NET. However, in some parts of the program, a detailed comparison will find that applications that use Visual Basic .NET will have substantially improved performance than Embedded Visual Basic.
Q: What is the difference between .NET CF and ASP.NET Mobile Controls?
A: There are two different options for mobile device development procedures. One is to run directly on the smart device; another is to let the program run on the server side, and display it through the browser. The .NET CF supports the former, and ASP.NET Mobile Controls (ie Microsoft Mobile Internet Toolkit supports the latter.
If the developed program requires running or requires more powerful user interface support without a network connection or requires closely related to the operating system, such as multimedia or other devices, use the .NET CF will provide the development of such smart device programs. The biggest convenience.
Of course, developing programs that are running in server segments also have a corresponding benefit. This structure is especially true for programs that need to have a wide range of procedures that need to be accessed through the network. Because the server side uses the same device as the desktop, these programs are not subject to resource limits. We generally use the ASP.NET Mobile Controls in Visual Studio .NET to develop relevant programs.
Posted on 2005 January 04, 5:09 PM
