The following summary describes tools currently available on Windows Mobile-based Pocket PC and Smartphone. When reading the instructions for reading, developers should put these tools to use this machine, hosted or server-side code to consider:
Using native code is to achieve high performance, when you need to directly access hardware or limited resources.
Using the hosting code is to develop applications centered on the user interface, this application requires soon as soon as possible or requires a quick development speed. If you want to access the web service easily, you can also use managed code.
Using server-side code is to develop applications for multiple devices using an code set, which requires sufficient data bandwidth.
Embedded Visual Tools 3.0
Microsoft Embedded Visual Tools 3.0 provides an integrated development environment for building a mobile application, including the necessary compilers, debugging, and platform documents. Embedded Visual Tools 3.0 includes Microsoft Embedded Visual C 3.0 (EVC 3.0) and Embedded Visual Basic 3.0 (EVB 3.0). Both tools are independent development environments and do not need to run any other development environment.
To develop Windows Mobile-based devices, all tools need to use the platform software development kit (SDK) of the target device. Embedded Visual Tools 3.0 2002 includes SDK for all Windows Mobile devices (including Pocket PC 2002 and Smartphone 2002). The SDK of the non-Windows Mobile Series should be obtained from the manufacturer of the device.
Embedded Visual C 3.0
The Microsoft Embedded Visual C 3.0 development system provides the C compiler of this machine code based on Windows Mobile. If the correct SDK is installed, it can be used to develop applications for all Windows CE 2.11 and 3.0-based devices. The Embedded Visual C debugger works through Microsoft ActiveSync.
In addition, it also provides software emulators that can be used in Pocket PC 2002 and Smartphone 2002 devices. When Pocket PC 2002 is released, Microsoft has introduced a new emulator for Pocket PC 2002 SDK, which is closer to true Windows Mobile-based devices. This new emulator can run a real Windows CE binary file in a virtual PC Shell. SMARTPHONE 2002, Pocket PC 2003 and SMARTPHONE 2003 SDK also use this new emulator.
Embedded Visual C can be used:
Pocket PC or any other Windows Mobile-based driver
Applications running machine on the device
Use high-speed graphic games through Game API (GAPI)
Applications with high processing requirements
COM server or Microsoft ActiveX control
Embedded Visual Basic 3.0
Embedded Visual Basic 3.0 supports applications written in Visual Basic language, which is explained at runtime. Although most Windows Mobile-based devices have built-in features to run applications built using Embedded Visual Basic, some custom Windows CE-based embedded hardware platforms may not include Embedded Visual Basic runtime. The Pocket PC's Windows Mobile 2003 software does not contain Visual Basic runtime, but you can download from Windows Mobile Developer Downloads. Embedded Visual Basic is a scripting language instead of a Visual Basic language with all functions. Therefore, many language features provided for desktop systems in Visual Basic 6.0 are not supported in Embedded Visual Basic 3.0. E.g:
1. By default, all variables are Variant types, and strict types are not supported.
2, you can't use the Embedded Visual Basic to develop ActiveX controls, but you can integrate several
3, the original control of Visual Basic is not supported, and some attributes are still missing
Embedded Visual Basic cannot be used to develop applications for Windows Mobile 2002-based smartphone. In view of this, in addition, other reasons (including further developing the Visual Basic .NET development group), Embedded Visual Basic technology has gradually been eliminated, and it is replaced by a more powerful Visual Basic .NET language. Microsoft recommends developers to create all new Pocket PC applications using Visual Basic .NET, using Embedded Visual Basic to maintain early versions of applications.
Embedded Visual C 4.0
Microsoft Embedded Visual C 4.0 supports new Windows CE. Net 4.2 devices, and after installation of released service packs, support for Windows Mobile 2003 software for Pocket PC and Smartphone (previous code name "Ozone"). Embedded Visual C 4.0 is an ideal software that uses this unit code on Windows CE .NET 4.2 for mobile or embedded devices to develop applications. Enhanced features of Embedded Visual C 4.0 include:
1, real-time debugging to diagnose unprocessed abnormalities
2, C structured abnormalities
3, "appended to" process to get enhanced process debugging capabilities
4, better integration with new emulators
Visual Studio.net2003 Smart Device Programmability features
Visual Studio .NET SMART Device Programmability (SDP) feature (previously called Smart Device Extensions [SDE] can help developers write mobile applications with Microsoft .NET Compact Framework, enable distributed in the case of connection or disconnection Mobile calculation. Using a large number of libraries provided in .NET Compact Framework, developers write more speeds that can be much faster than using traditional tools.
Using Visual Studio .NET 2003, developers can develop Pocket PC 2002 (if appropriate SDK) and Pocket PC and Smartphone 2003 are developed using the same tools and techniques used in desktop system development. It will be installed .NET Compact Framework, which is designed for devices specifically for resources. Developers can develop mobile and embedded devices using new C # languages or Visual Basic .NET languages. It can also be well used to use XML Web Service or ADO.NET applications. Visual Studio .NET 2003 is available for:
1. Use the application of Web services
2. Applications that must be run in the connection or disconnection environment
3, use Visual Basic .NET or C # to develop applications
4. When you want to use the same tool to make desktops, servers and devices
5, rapidly developed mobile app
6, providing a reliable and secure environment
Applications that can be ported to different devices with different CPUs or various Windows versions
ASP.NET Mobile Controls
ASP.NET Mobile Controls (previously known as Microsoft Mobile Internet Toolkit [Mmit] is a supplement to Smart Device Programmability and .Net Compact Framework. ASP.NET Mobile Controls Send marks to a variety of mobile devices by enabling ASP.NET, thereby extending .NET Compact Framework and Visual Studio .NET builds a function of moving web applications. Using this method, developers can use Visual Studio .NET to build a mobile web application that automatically adjusts their page rendering to accommodate various devices, such as enabling Internet mobile phones, pagers, and PDAs (such as Pocket PC, etc. ). It also simplifies development tasks because it is integrated into the Visual Studio .NET Integration Design Environment (IDE), allowing developers to build mobile web applications by dragging the control to the mobile web form.
ASP.NET does not have any components on the client device. Instead, it uses server-side logic to accommodate the rendering of a web browser of a particular device. It can generate wireless tag language (WML), HTML, and streamlined HTML (ChTML).
In addition to the highly adaptive web page presentation, ASP.NET also provides a rich framework for customization and scalable, and provides a simple way to extend control, so that the control can accommodate each will be listed. New equipment. In addition, ASP.NET also allows developers to control rendering of specific devices or device categories within the same programming model, allowing developers to easily add support for new devices without having to reply their mobile web applications.
ASP.NET Mobile Controls can be used:
1. Support various devices that enable web (mobile phones, pager, PDA)
2 Support various markup languages (WML, Chtml, HTML)
Note: ASP.NET Mobile Controls does not need to install any client. However, the target device must have a client web browser.
Microsoft SQL Server 2000 Windows CE Edition 2.0
Microsoft SQL Server 2000 Windows CE Edition (SQL Server CE) 2.0 is a streamlined database that can be used to rapidly develop applications that extend enterprise data management capabilities to mobile devices. SQL Server CE is a powerful tool that supports user familiar structured query languages (SQL) syntax, and provides development models and APIs consistent with SQL Server, making it easy to develop mobile applications. The SQL Server CE engine provides a basic relational database capabilities such as optimizing the query processor and support for transactions and various data types, while it also maintains a streamlined memory space that retains important system resources. Remote data access and merge replication ensure reliable transmission of data in the SQL Server database; can be operated offline, but also synchronize with the server in the future, which makes SQL Server CEs to be ideal for mobile and wireless environments.
SQL Server CE 2.0 can be integrated with .NET Compact Framework through Visual Studio .NET, simplifying database applications for smart devices. Using the new SQL Server CE data provider via the public language runtime management code, the mobile application developer can establish a highly scalable application with offline data management functions in the case of disconnection.
In the following cases, SQL Server CE can be supplemented by the development tool:
1. Expand the enterprise data management function to Pocket PC
2. Develop applications that store and process a lot of data on mobile devices
3. In an environment where the connection condition is unstable, it is necessary to use a mobile device to perform reliable data replication.
Tool comparison table
Development program
In the short term, the most common tool for developing Windows Mobile devices is still an Embedded Visual Tools 3.0 for Pocket PC 2000 and 2002 for SmartPhone 2002 Embedded Visual C 3.0, and Embedded Visual C for Pocket PC and Smartphone 2003. 4.0. Finally, Visual Studio .NET and its SMART Device ProGram Mability (SDP) feature will become all development platforms based on Windows Mobile devices.
Server-side code or client code?
Using server-side code or using client code, depending on several conditions. The application's scheme is different, but these conditions can help you choose the best solution for your application.
User experience: Client applications generally provide better user experience because they run on the device and independently of all infrastructure interoperable.
Available bandwidth: This is related to the user experience. Applications running in a sufficiently reliable bandwidth environment (such as wireless LAN), if you use server-side code, you can also provide a good user experience.
Data security: The client application must ensure the security of sensitive data on the device. A series of Cryptographic Service Provider provided by Windows Mobile software helps achieve this. Server-side applications must ensure that data can be securely transmitted using SSL and other technologies.
Supportability: Updates to client applications must be downloaded and installed on the device. If you develop a client application, please take this factor.
Offline function: If you need offline data access and other offline functions, the client application is the best choice.
What do you need to prepare before developing Windows Mobile-based Pocket PC and SmartPhone?
Before developing Pocket PCs and SmartPhone, what you want to prepare depends on what you want to develop, and to develop. In most cases, you need an integrated development environment, as well as the SDK or extension of the device to be developed. Fortunately, you can develop all Windows Mobile-based devices on a computer because all tools can coexist on these two devices. See Appendix on our recommended installation order. Currently, Embedded Visual Tools IDE and the desired SDK are free, you can download it through web.
Who when?
Performance, control or resources are very important to me. For example, I want to write a game, device driver or an Active X component ...
If you plan to develop Pocket PC and Smartphone running Windows Mobile 2003 software, just download Embedded Visual C 4.0 Service Pack 2 and Pocket PC 2003 SDK from developer Downloads. You can also develop Windows Mobile® 2003 software for Smartphone using Smartphone 2003 SDK.
To support early Pocket PC, Pocket PC 2002, and Smartphone 2002 devices, you also need to download Embedded Visual Tools 3.0 - 2002 Edition.
If you need to maintain the development of Handheld PC Professional Edition, Handheld PC 2000, or Palm Size PC 1.2, you can download SDKS for Embedded Visual Tools 3.0.
I want to quickly develop applications in a safe and reliable environment, I may have to access Web services ...
I want to write a client application with the largest code portability ...
I want to take advantage of the Visual Studio .NET 2003, Visual C #, Visual Basic.net or .NET Framework knowledge ...
We recommend that you use the Smart Device Programmability feature in Visual Studio .NET 2003. The .NET Compact Framework is built into the Windows Mobile 2003-based Pocket PC and Smartphone. It can be used for Pocket PC 2002, but must be installed on the device.
I want to develop SmartPhone 2002 ......
You should download Embedded Visual Tools 3.0 - 2002 Edition.
If you want to test your app on a real device, your area has no Smartphone, or Smartphone does not support development, you can purchase Smartphone Developer Kit.
I want to use a code library to develop Pocket PC 2002 and Pocket PC 2003 ......
You can build your app in two ways:
Develop .NET Compact Framework using Visual Studio .NET 2003. This way, you can write a hosted code base and let it run on both devices. Pocket PC 2002 requires installation .NET Compact Framework on the device.
Use Embedded Visual C 3.0. If you use a reliable API and write a well-running application, and use Embedded Visual C 3.0 to write and compile the native code, it should be able to run on both Pocket PC 2003 and Pocket PC 2002. I want to use a code library to develop SmartPhone 2002 and Smartphone 2003 ......
.NET Compact Framework cannot be used for Smartphone 2002. To write a code base to run on Smartphone 2002 and SmartPhone 2003, you must use this unit code and compile your application with Embedded Visual C 3.0.
I want to maintain applications written in Embedded Visual Basic ...
You should download Embedded Visual Tools 3.0 - 2002 Edition, which contains the development environment of Embedded Visual Basic, emulator, and SDK.
Consider using Visual Basic .NET 2003 to export the application to .NET Compact Framework.
I want to write applications for various mobile devices that can run in thin client environments. I want to maintain applications written in Embedded Visual Basic ...
You should use ASP.NET Mobile Controls in Visual Studio .NET 2003.
Note: This article is reproduced from www.mypda.com.cn
