Use the wince 6.0 Simulator

Use the wince 6.0 Simulator

In the previous article we introduced how to build wince6.0 development environment, installation process please refer to: http://blog.csdn.net/htttw/article/details/7323201

After wince is compiled

C: \ wince600 \ osdesigns \ osdesign1 \ osdesign1 \ reldir \ deviceemulator_armv4i_debug (this is my path) to generate NK. bin. If a Board is installed with bootloader, you can directly run it on the board. The effect is the same as that of our simulator.

Today we will introduce how to use the wince simulator, but we will first introduce how to generate the SDK,The SDK is a development kit. Because each Board (or simulator) is customized differently(Or simulator)There is a corresponding SDK, so that other developers can use this SDK to develop on our boardApplications running on (or simulators)Program.

Click the menu item --> Add new SDK, and fill in some basic information in general, as follows:

Click build all sdks under the generate menu, and vs2005 will start to compile the SDK, and it will soon be ready. Stickers:

After compilation, *** is generated in c: \ wince600 \ osdesigns \ osdesign1 \ osdesign1 \ sdks \ sdk1 \ MSI (this is my path ***. MSI file. This is our SDK.

Installation:

Follow the steps below to proceed:

After the installation is complete, open vs2005, open the device emulator manager in the tool menu, and you will see our SDK:

Below we use this SDK to develop our first application:

(In this example, when I started using the simulator, right-click and the mouse did not respond. It turned out that I was stupid. As long as the left-click button takes a little longer, the right-click menu will appear, haha)

The development of applications under wince is actually similar to that of the PC version. Here we take the MFC as an example.

Open vs2005, file --> new, as shown below, named mytest

In the SDK step, select our own SDK. For details, referHttp://blog.csdn.net/htttw/article/details/7323201

Select the application type based on the dialog box, and then retain the default value.

Now that the template is ready, let's run it in the simulator. Directly click the "start debugging" button in vs2005, the simulator window will pop up automatically and our application mytest will be opened,

I believe that the previous students with the foundation of MFC programming will know how to do it.

Next, we place a button on the main interface. A message box will pop up when you click the button.

Return to vs2005 and add a button on the dialog (note that there are two dialog s that should be modified on the dialog without the wide suffix)

ThenAdd a click event handler, Enter the following content:

 
MessageBox (L "this is my test! ", L" Haha ", mb_yesno | mb_iconstop );
 

Then run it again,

Now let's run it separately in the simulator. We use the SD card method described above (shared folder on the general page ):

Copy EXE directlyIn the shared folder, open it in the simulator (here I copied it to the simulator), as shown below:

Finally, we will introduce how to set up our simulator:

Under connectivity options in the target menu of vs2005, click the Settings button next to download to bring up simulator settings,

In general, you can set the memory, flash disk, and shared folder of the simulator:

Note: The Shared Folder above indicates that this directory is the SD card of our simulator, so the files in this folder are stored in the SD card of our simulator. Flash memory file indicates that the content in the NAND flash of our simulator will be saved to this file (if this item is set, the save in the Flash menu of the simulator will be available)

Set the width and height of the simulator in display:

Set the network connection of the simulator under the network. If we want the simulator to have the network function, set it as follows:

Peripherals is used to set peripherals, mainly for serial ports. Because I do not have a serial port, it is not displayed here. Otherwise, there should be options similar to COM1 and com2.

Done!