Publishing the Project
Publishing the project creates a read-only version of the project.
It is NOT necessary to publish the project to install it for production. In scenarios that you intend to have continuous changes to the project in field, it is simpler to put the main project file, TPROJ, directly on the production computer.
The benefits of publishing is that the system created a compacted and real-only version of the project file. The file created has the same name of the project file, with the publish version number and the extension TRUN.
This allows the system to comply with regulated industries.
The typical scenarios to the publish command are:
•You want to deploy a read-only version of the project, for instance to be in compliance with certified and regulated environments.
•You want to use the automatic version numbering system. The result of publishing is a .TENG file that also contains a major (1.0) or minor (0.1) version number as part of the file name. In addition, Info > Track helps you manage the files published to the field, including which project build they are.
•You want a smaller footprint and faster loading of the project, for instance on machines, OEM and embedded systems. The TRUN file can be up to 5 to 10 times smaller than the TPROJ file.
•You want to protect the project from modification.
Caution: The TRUN file is always read-only, but if the project configuration will not be visible to end-user, it is an independent option defined in the Security System. If you don’t want end-users to see the project configuration remove the permission of the GUEST user and other users to edit the project before publishing it.
To publish the project:
1. Go to Run > Build > Messages.
2. Select the desired build settings and Click Build.
3. Go to Run > Publish.
•The Current Project Settings fields show the read-only status of the project.
4. Select the Publish Settings you want.
5. Click Publish.