VS.NET development introductory and Win CE development advice
VS.NET development
I came to our .Net time, how do I say? It's all, everyone is blocked by java and .net? No matter how everyone is noisy, .Net Compact Framework is undoubtedly a big gospel for embedded programmers in their hands. Visual Studio .NET 2003 fully supports the development of mobile devices, well, let us start a fantasy .NET tour.
Open vs.net 2003, select File - New - Project, open the above interface. Let us build a Visual C # project, then select Smart Device Application, then OK.
You are here to choose a target device: Pocket PC, Smartphone, Windows CE (referring to other platforms), the following is the selected engine type, we select "Windows Application", the left is the simulator supported by the selected platform. Finally click OK, we can enter the main interface of VS.NET.
Selecting the output device and the EVB is very similar, just select the output device without selecting the CPU type. Of course, because .NET is running on the virtual machine. In the CPU type, there are many embedded fields, .NET and JAVA can truly play their strengths.
Of course, we can also choose VB.NET as the language of the development of smart devices, the situation and C # is exactly the same. At present, smart devices have only support C # and VB.NET. Programmers with hobbies C may have to wait for a while.
Advice developed by Windows CE
It can be said that when we spend most of the time to port existing applications into Microsoft Windows CE. Generally speaking, this plan is not too difficult. We started to Microsoft Win32 code, and of course Windows CE is a Win32 application interface (API). Advantageously, our application (ie RAIMA Data Manager) has a convenient use interface and contains a library consisting of approximately 150 sub-functions, which are written by C language, which can be used to create, manage, and access. database.
According to the way of establishing an application, we originally ported it into Windows CEs and is a relatively simple C language programming practice. However, we have encountered some difficulties soon. Starting from a careless mistake, such as using the Microsoft Windows NT library on Windows NT-based Windows CE emulators, then violate Windows CE programming arms, such as "Don't give Unicode (International Standards Organization 10646 standard) character assignment odd numbers Memory address.
About 90% of the problem is more or less related to Unicode. Although Unicode programming is not difficult, it is easy to make an error when writing code to the single-byte character (I have many mistakes).
The following advice is based on our experience in writing RAIMA Data Manager on Windows CE, but I believe that they are worth learning from any other Windows CE program. After all, most of the Windows developers, when they create the first Windows CE application, truly use the win32 knowledge that has been mastered.
- Reprinted from blue ideal digital station
