---
title: "Project"
canonical: "https://docs.cuesystem.com/space/CVCIDE/498533391/Project"
format: markdown
---
> Macro (toc)
---
# Build
This item builds (compiles) the project source code/data to check for syntax errors. Programmers can build the project repeatedly, at each step in their development process. The building is a process that allows for compile-time error correction. These errors can include incorrect syntax, misspelled keywords, and type mismatches. Errors are displayed in the Output window. Errors are displayed in the output window.
# Debug
This action compiles and starts application of selected unit. it builds source code and launches debug mode with touch panel or controller simulation. Errors are displayed in output area.
It allows you to **create a configuration** with different debugging profiles too.
Debugging is a two-step process:
1. The project build is provided for compile-time error correction.
2. The debugger is used to detect and correct such problems as logic errors and semantic errors that are detected at run-time.
Use Debug item and select the unit which will be debugging. The list of units contains all CUEunits used in the project.
Debug is stopped by the Stop Debug menu item.
### Debug configuration
Debug mode can be configured using item Configuration ... Following window is opened. You can enable/disable Display Debug Messages.
Use the button New ... to create a new debug configuration. Define the name of the new configuration and click OK.
You can choose to debug mode and enable/disable display debug messages for the new debug configuration as described in the following picture.
#### Debug modes
Debug modes available for every CUEunit are as follows:
- **None **- CUEunit is not debugging in this debug configuration.
- **Simulation **- CUEunit is simulated on your PC.
- **Hardware **- CUEunit is debugged using hardware (real unit). First, the compiled program is uploaded to the CUEunit. Next, the program is started.
It is possible to combine different modes for CUEunits used in the project. For example, it is an advantage to debug the touch panel in Simulation mode - then it can be fully controlled from the PC. On the other hand, if a controller is debugged in the Hardware mode, it can control physical devices, read inputs, etc.
### Simulation Windows
The following picture shows the touch panel and controller debug, both in Simulation mode.
Zoom in and zoom out the touch panel window by rolling the mouse wheel. Ctrl+0 returns this window to the original (native) zoom.
The controller window displays all front panel indicators and it is simple to check the status of all control ports.
### Debug messages
If debug commands DebugPrint or DebugPrintFormat are used in your program, all debug modes support debug messages displayed in the Output window. For more details about debugging, commands see the Programming Language XPL2 section.
# Final
The final menu item builds source code and uploads final binary files (.cvca) to hardware units or export all applications to individual .cvca files. Click Final and the following window appears.
### Upload
For application upload to your hardware units use checkboxes to select units you want to upload and then click the button Upload checked.
First CVC checks the version of the CUEunits firmware. If the firmware is not current, then CVC updates the firmware automatically. If the firmware is current, application upload is started.
### Export
For application, export using the button Export As.
The application can be exported as:
- **Application Files Package** - file *.cvcx contains all CUEunit applications. Then project can be uploaded using special simple application CVC Application Loader (without necessity to have full Cue Visual Composer).
The Application Loader is .exe file and it can downloaded here: [https://cuesystem.com/EN/Downloads](https://cuesystem.com/EN/Downloads).
- **Application Files** - every CUEunit is exported to a separate file *.cvca. This file can be uploaded to the hardware using Admin Web.
- **CUE Solution project** - file *.cuesolutionproject contains all CUEunit applications. Exported file can be used in CUE Solution server. Supported since Cue Visual Composer 21.10.
- **Applications and firmware to folder for FTP server **- every CUEunit is exported to separate file *.cvca together with firmwares and configuration file. This kind of exporting is for updating applications by FTPS server [https://cue.atlassian.net/wiki/spaces/CVCBP/pages/504856612/Administration+of+large+projects#Update-project-instances](https://cue.atlassian.net/wiki/spaces/CVCBP/pages/504856612/Administration+of+large+projects#Update-project-instances)
# Multi Configuration …
Different project configurations can be created in this section. In the different configurations, it is possible to set different **IP addresses** and **Magic names** for the upload of the application to the individual CUEunits.
Multi configuration is typically used when the same project is used for multiple identical installations, e.g. multiple identical meeting rooms, classrooms, etc.
When uploading an application using the **Final **action, it is then possible to **select a specific configuration** from a list of prepared configurations and it is not necessary to set the IP Addresses and Magic names of all units used in the project before each upload.
# Export Panel As Demo
This item exports the selected touch panel as Windows executable file *.exe. The file can be used for demonstrations, approval processes, etc.
Select CUEunit you want to export and then use the dialog box and define the file name and location.
> 📝 For distribution, it is recommended to compress the file in ZIP or another compressed format.
# Export All Source Codes …
This action exports all source code as ***.txt** files. The files are organized in the Instances, Devices, CUEDevices, GraphicCollections, and Applets folders.