EVB / EVC development entry
EVB development entry
Microsoft has announced that EVB no longer supports Windows CE.NET, so the final version of EVB is 3.0. However, due to the characteristics of EVB's easy-to-hand, it has become a rapidly developed unblocation of the Windows CE platform before VS.NET is shipped. Evb is still suitable for rapid development of small applications on the Windows CE 3.0 platform. If you are not a full-time Windows CE programmer, just need to develop a part of the entire system on the Windows CE platform, then EVB allows you to develop your you want with a short time.
EVB's development environment is also very simple, you can download EVT 2002 from Microsoft's website, which contains EVC 3.0, EVB 3.0, and Pocket PC 2002 SDK and Smartphone 2002 SDK. Follow the prompts to install the EVB and Pocket PC 2002 SDK. The SDK contains an emulator. In the case of no actual devices, the simulator can be used to debug the program.
It should be noted here that the development environment and the simulator communicates between the network connection protocol, so there must be an active network connection on the computer used. If not, you can install Microsoft's virtual network card.
The EVB development environment is similar to VB, because the Windows CE application needs to debug on the simulator or actual device, so we must select the output target of the program. If you select emulation, after you press (or F5), the EVB will automatically start the simulator and download the program to the simulator.
Since new Windows CE.NET will no longer support EVB, Microsoft recommends that the EVB programmer uses VB.NET to develop new programs, and for the original EVB program, the migration path is given, about this discussion, you can refer to MSDN article "Moving from Embedded Visual Basic TO Visual Basic .NET".
EVC development
Whether it is a Win32 platform or a WinCe platform, Visual C is a powerful development tool. And EVC is also a mainstream development tool on Wince. The EVC supports the subset of the MFC class library, which provides developers to provide the most powerful support, making the VC programmers on the Win32 platform can easily migrate to the WinCe platform. However, since the MFC class library requires a DLL, this is a big burden for some embedded devices for some storage space, so Smartphone does not support MFC.
Said so much, let us create an EVC project. Is it very similar to VC, you need to remind you that it is necessary to choose the CPU type supported by the project while choosing the CPU type of the embedded device. The process of creating a project is the same. Of course, different platforms support engineering is different, such as Pocket PC 2003 has two projects supporting MFC and APIs, while Smartphone 2003 has only one project that supports API.
The EVC is more than a row of drop-down menu than the VC environment, which is used to select: Engineering, SDK, CPU types, and output devices. Take the Pocket PC as an example, debugging on the actual device should select Win32 (WCE ARMV4) Debug, and on the simulator, Win32 (WCE Emulator) Debug is required.
- Reprinted from blue ideal digital station
