Testing and Running Projects
The Run environment provides access to all Project execution features.
Build
Build compiles all displays and scripts for final verification before deploying a project for production. Build provides complete verification of the application logics when preparing for final production, but is not necessary during development as all modifications in the project are automatically and transparently being compiled in the background while you are editing.
Testing the Project
Test lets you run the project in Test mode, which means enabling protections that allow it to run even on the same machine that the project is running in Startup. The Historian and Alarm logging functions are directed to use temporary files instead of the defined database for the project production.
Optionally you can enable diagnostic tools to help resolve any issues you may be working through. You can also decide which modules will run during your test.
Project Startup
Startup is where you configure how your project will run in production mode. This means enabling the Historian and Alarm logging functions to use databases as defined in the project instead of the temporary files used in Test.
The Online Configuration checkbox allows you to establish on-line configuration. When the Project is running you can attach to the execution, which means modifications to the project we be shown in the running project when made.
Publishing the Project
Publish creates a read-only protected version of projects suitable for deploying in the field.
When the Publish command is executed a new Project file (with extension "teng") is created with the version number selected.
The Published Projects ("tproj" extensions) are similar to the current project (".proj" extension) and can be opened only in read-only mode. This provides you with a safe backup version of published applications.
