How to expand the storage space of the Windows Mobile Simulator

Windows Mobile appProgramAt the early stage of development, you can use the simulator provided by the SDK for debugging, which provides a convenient way for our developers. For general applications, the space occupied is several hundred kb or several MB, which is not a problem in the simulator debugging. However, sometimes, if the program to be installed or the program to be debugged exceeds a certain size, it cannot be debugged according to the default system settings. Why? This is because we have packed a large number of DLL and resource libraries, so that the system's storage space is exhausted. Pass this articleArticleTo get rid of the limitations of the simulator storage space.

1. Windows Mobile simulator storage space browsing

First, let's take a look at the default storage space of the Windows Mobile simulator. The following lists the memory setting of simulators in pocketpc 2003se emulator, Windows Mobile 5.0 pocketpc R2 emulator, Windows Mobile 6 Professional emulator, and Windows Mobile 6.5 professional emulator:

Figure memory settings of four WM Simulators

As shown in figure 1, apart from pocketpc 2003se emulator, users can adjust the storage and program space ratios. The storage sizes of the other three simulators are 32 MB, the user cannot adjust it, but the size of the program is indeed different. Next, let's take a look at how to scale the memory of these WM Simulators of different versions.

2. Memory Extension Method of WM Simulator

2.1 program memory Extension Method

For the program storage part in the simulator, we can change it Through Visual Studio settings. This method is applicable to the above four simulators. Use the tools-> options-> device tools-> devices menu to select the target simulator. Take Windows Mobile 6 Professional emulator as an example. Click the properties menu on the right, in the displayed dialog box, select "emulator options" and fill in the required storage space in "specify Ram size". Here, I enter 256. After restarting the simulator, we can see that the size of the program has changed. See Figure 2:

Figure 2: Use emulator options to change the size of Program Space

2.2 using storage card for expansion

Sometimes we need to install some applications on the simulator for testing, which can be extended through storage card. This method is applicable to the above four simulators. The specific method is as follows: Select File> Configure> General> shared folder of the simulator, select a folder in the local PC, and map it to the storage card of the simulator. As shown in 3:

Figure 3: using storage card for expansion

2.3 change the program debugging directory for extension

In the Windows Mobile project we created, the default program debugging path is my device-> program files, as shown in 4:

Figure 4: default program debugging path

However, sometimes the applications we debug may occupy a lot of space. If the storage limit is exceeded (32 MB), debugging will certainly fail. Since the storage size is 32 m and hard code has been reached, can we change the program debugging path and map it to the local PC folder? The answer is yes. The specific method is as follows: click "Project Properties" (note that it is not Solution Properties) to change the output file folder in the device, for example, to "\ storage card, when you debug the program, it will be downloaded to the storage card, and the storage card has been mapped to the local PC file by way of method 2.2. Therefore, we do not need to be limited by 32 m storage space. As shown in figure 5:

Figure 5: Change the program debugging directory for extension

2.4 change the ratio of storage to program in pocketpc 2003se emulator.

In pocketpc 2003se emulator, if you need to debug a large program, we can increase the ram space by using method 2.1, and then change the ratio of storage to program to expand storage. See Figure 6:

Figure 6: pocketpc 2003se emulator expands Storage

3. Summary

This article summarizes four methods to expand the storage space of Windows Mobile, especially the third method. In the debug phase, if the application to be debugged occupies a large space, this method can be used for debugging. I hope the methods I have summarized here will be useful to many Windows Mobile developers.