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

Editor to share with you the compatibility of C# Windows CE features of the example analysis, I believe that most people do not know much about it, so share this article for your reference, I hope you will learn a lot after reading this article, let's go to know it!

The design idea of the compatibility of C# Windows CE features:

Portability allows us to migrate code from the desktop to C # Windows CE, or between C # Windows CE devices that use different CPU.

Compatibility of the programming interface means keeping the device interface consistent with the desktop interface as much as possible. To this end, the C # Windows CE development team took the concept of portability a step further, making it as easy as possible to share code between desktop environments and smart devices.

In some cases, the desktop environment corresponds to the features of C # Windows CE. For example, file systems, C # Windows CE and desktop environments all support hierarchical file systems with long file names; the supported * * file paths are all 260 characters long. Moreover, they use a hierarchical registry for both management systems and application settings.

The choices made for each different programming interface further enhance compatibility.

Since C # Windows CE supports fewer Win32 functions than the desktop environment, those matching functions are the same as those corresponding to the desktop environment as much as possible.

For example, the desktop version of the create window (CreateWindow) function and C # Windows CE have the same number and type of parameters for the same function.

It seems reasonable for the new operating system to be compatible with the original version, but this is usually not the case. The OS/2 operating system, for example, was jointly developed by Microsoft and IBM as the successor to Windows.

However, Presentation Manager, a GUI programming API, is "mixed" and "improved" with Win16 API on its original basis. as a result, this new API has lost all contact with Win16 API, which is a complete replacement and not compatible.

This is problematic because there is a lot of Win16 code and there is very little Presentation Manager code associated with it.

Many developers find it almost as difficult to port Win16 code to the Presentation Manager platform as it is to migrate the same code to other GUI systems such as Macintosh. In order to solve this problem, Microsoft has developed Win32, a new programming interface, whose primary goal is to maintain consistency and compatibility with Win16 API. From this profound lesson, we have a deeper understanding of the efforts that need to be done to successfully upgrade API.

The C # Windows CE development team benefited from this experience and fully enjoyed the benefits of easily porting Win32 software from the desktop.

The .NET Compact Framework has similar compatibility issues. The .NET Compact Framework development team tries to maintain consistency between the .NET Compact Framework and the .NET Framework. As described later in this chapter, the .NET Compact Framework and desktop versions have many common elements, such as common namespaces, classes, properties, methods, events, and so on.

The above is all the contents of the article "sample Analysis of the compatibility of C# Windows CE Features". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.