Shulou(Shulou.com)06/02 Report--

This article mainly explains "what are the characteristics of C#Windows CE". The explanation in this article is simple and clear, easy to learn and understand. Please follow the ideas of Xiaobian and go deep into it slowly to study and learn "what are the characteristics of C#Windows CE" together.

A successful operating system must be unique in the availability of two critical software: applications and device drivers.

If there is not a certain amount of each type of software, the operating system's capabilities are bound to be limited. In order to solve this problem, Microsoft has done a lot of work to enhance the portability of existing software to C#Windows CE, so that software developers can easily utilize existing successful software while building a successful C#Windows CE environment.

First, Microsoft sets the Win32 API as the programming interface for C#Windows CE applications and device drivers. As described earlier in this chapter, the Win32 API has played an important role in all Microsoft Windows operating systems since its introduction in 1992, and C#Windows CE is no exception.

In C#Windows CE, other desktop versions of the programming interface are also available. This includes the MFC library, which provides object-oriented Win32 APIs for C++ programmers. Also included is the ActiveX Template Library (ATL), *** libraries that support simple ActiveX controls in Internet Explorer. There is also eMbedded Visual Basic, which is a stripped down version of the desktop Visual Basic environment. (Pocket PC 2003 will be *** eMbedded Visual Basic enabled, and in the future eMbedded Visual Basic programmers will need to switch to the. NET Lite Framework or use third-party tools like NS-BASIC10.)

To support the development of new device drivers, C#Windows CE device drivers follow the desktop version of Windows NT/2K/XP driver model as much as possible. This is becoming a reality in network (NDIS) drivers, as well as device drivers for display terminals, printers, keyboards, and USB. The basic approach to these drivers is to simplify and reduce the desktop version of the corresponding driver. The driver design guidelines and architecture are included in the desktop version of the driver, but it is better to encourage desktop driver authors to develop device drivers based on C#Windows CE.

The Win32 API is designed as a portable programming interface that enables source-level portability between different CPU platforms11. The goal is to make independent subject source code run on different CPU environments after recompilation, which is mostly already a reality in C#Windows CE. Almost every C#Windows CE developer has taken advantage of this design, sometimes even thoughtlessly. Suppose there is a developer who develops software for StrongARM based Pocket PC, how does he benefit from source code migration? Obviously, if he can reuse code from the desktop version (or server version) of Microsoft Windows, then he has benefited.

In addition, it can also use Pocket PC emulators running in x86-based development environments. The emulator runs the same software as Pocket PC in a window on Windows 2000 or Windows XP. Pocket PC programs actually use native x86 instructions when they run on emulators; the same program compiles and runs on a real Pocket PC device using its StrongARM (or XScale) processor, although the program may need to be recompiled as a StrongARM executable.

The. NET Compact Framework takes portability a step further by supporting binary portability between different processor platforms. Once compiled, stand-alone. NET Lite Framework (.exe) programs can run unchanged on any processor supported by the. NET Lite Framework environment, such as StrongARM, MIPS, SH3, SH4, and x86 CPUs. In addition, the same executable program can also be run in the desktop version of Windows. NET Framework version 1.1 12.

There is a reason for this. First, compiling. NET programs differs from C or C++ programs in that the resulting executable files are not CPU-specific machine code, but CPU-independent machine-level languages, namely Microsoft Intermediate Language (MSIL), sometimes called Common Intermediate Language (CIL).

The second factor that allows. NET Lite Framework programs to run in the desktop version of. NET Framework is the compatibility of the C#Windows CE programming interface with the desktop version programming interface, which we'll cover shortly.

Thank you for reading, the above is the content of "C#Windows CE characteristics are what", after the study of this article, I believe that everyone has a deeper understanding of what C#Windows CE characteristics are, and the specific use situation needs to be verified by practice. Here is, Xiaobian will push more articles related to knowledge points for everyone, welcome to pay attention!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.