Development of Wince applications

Wince ApplicationProgramDevelopment is an important part of Wince development. This article briefly introduces some basic concepts of Wince application development.

Let's talk about development tools first. Currently, many development tools are used: evc4 (SP4), vs2005, vs2008, and platform builder.

Among them, platform builder is mainly used to customize the operating system. Although it also supports writing applications, it is rarely used. If you do, you have to compile the system before creating an application project.

Vs2005 and vs2008 are Microsoft's integrated development tools, and pb6.0 is installed as the vs2005 plug-in (pb6.0 currently does not support vs2008 ). In vs2005, You can compile the wince6.0 operating system or the applications on the device, saving the trouble of switching the development environment.

Evc4 (SP4) is an embedded VC, which is basically the same as vc6.0.

Compared with the development of desktop Windows applications, the development of Wince applications has the following features:

1. Unicode encoding. The applications in wince can only use Unicode encoding, while the desktop system supports Unicode and ANSI codes. Note This when porting a PC program to a device.

2. SDK. SDK is the software development support package, which is indispensable for software development. However, it is particularly important in the development of Wince applications. Because the wince system itself is a non-standard operating system, its component features and scalability determine that different systems support different APIs. As the desktop system is relatively standard, the function of the SDK is weakened. After compiling the system, the SDK in wince is exported through platform builder. Application developers install the SDK, write the application, and finally download the application to the target platform to run the test. In general, sdks are the bond between applications and operating systems, but they are not exactly one-to-one. For example, when the hardware and operating system are not properly debugged, we can use the standard SDK or the SDK of a self-built Simulator for application development. After the hardware and system debugging is complete, we can perform joint debugging. The application can be compiled based on the new SDK, and can be run without re-compiling. Of course, an application runs well on another device, but it does not work on another device. Just as many WM applications cannot run in wince, although the kernel is the same, but the systems are different, the supported APIs are also different.

Finally, let's talk about the development language. The development of Wince applications involves Win32, MFC, and managed. For developers, it mainly depends on the efficiency, development efficiency, and running efficiency. According to the law of conservation of energy, the development efficiency and operation efficiency should be a shift-long relationship. Is it related to the conservation of energy law? Barely find a strong evidence. ManagedCodeBut the execution efficiency is relatively low. This is especially prominent in the case that the materials are not very rich embedded systems, and the real-time performance is not guaranteed. MFC is a basic class library based on window32. It encapsulates many Win32 APIs for developers to use, but it also has shortcomings and does not seem to be updated. Win32 is the most underlying of the three. The compiled program is small and runs fast without additional burdens. Therefore, the development difficulty is naturally high and the amount of code is also large. When developing an application, we should select a more appropriate one based on the actual situation.