| **Navigation:**  [[clarion.htm|Clarion.Net (Clarion#)]] > [[clarion net language reference.htm|Clarion# Language Extensions]] > Clarion.NET FAQs > Compact Forms >====== Creating a DESS File ====== | [[compact forms quick start.htm|{{btn_prev_n.gif|Previous page}}]][[clarion net language reference.htm|{{btn_home_n.gif|Return to chapter overview}}]][[working with the physical device.htm|{{btn_next_n.gif|Next page}}]] |
|  ||

Normally, running and debugging a CF application on the device emulator is a very long process (Not only in our IDE but in the MS VS as well). In order to run a CF application, the user normally will have to wait until the IDE completes deploying the following files:

·The OS image BIN file.

·Compact Framework Version 2 extracted from the device's cab file. This is built-in for Windows Mobile 6, but PocketPC 2003 and Windows Mobile 5.0 only have Compact Framework Version 1 installed.

·For debugging, some additional DLLs must be deployed (including NetCFLaunch.exe).

·The Clarion Runtime Library.

·All required files of the project. (Located by default in the \bin\debug folder of the CF project).

Taking into account all these factors, we have introduced a new **Create DESS files** feature.

A DESS (Device Emulator Save State) file is useful when building and running Compact Framework applications from the Clarion.NET IDE. It is available from the **Device Properties** and **Deploy** dialogs.

If the '**Show device choices before deploying a device project**' is checked in the Tools > Options > Device Options > General dialog, the **Deploy** dialog appears where the user may choose a target device to run the application.

Pressing **Create DESS** creates the DESS file for the chosen device.

Pressing **Deploy** runs the application. All others steps are fulfilled automatically.

Creating a DESS is only needed to be done once for the device for that the user is targeting. The resulting DESS will contain the OS image, CF v2, and files for debugging.

This operation takes about two minutes. It's purpose is to save time during deploying files before running/debugging a CF application.