Overview
Within our platform, we offer an elegant solution for managing project versions. Through this sophisticated tool, the capability to create a read-only iteration of a project, gracefully transitioning it into its released phase.
On this page:
the Build Feature
The Build feature compiles all project's displays and scripts for final verification before deploying the project for production. Build provides complete verification of an application's scripts when preparing it for final production. However, this is not necessary during the development stage since all project modifications are automatically and transparently compiled in the background while a project is edited.
The section Build and Publish is presented on the following image.
| Index | Description |
|---|---|
| 1 | Build button - The Build command does not need to be executed after a project is edited as it happens automatically in the background. The Build command only needs to be used as a final verification before a project is deployed or for when a build number is needed. |
| 2 | If checked, a backup copy of this build will be created with the extension .dbbak |
| 3 | Be sure to use this option if you have made changes to the symbol library. This option applies to all symbol library changes throughout the project. |
| 4 | |
| 5 | Publish button create an only read version of this project, with the next configured version. |
| 6 | Option used for managing project versions. |
| 7 | Option used for managing project versions. |
| 8 | This table shows the current status of each script and display potential errors or warnings. |
| Executing a Build is useful for achieving complete verification of an application's logic when an application is being prepared for final production, but it is not necessary during the development process. Any modifications you make on a project are automatically and transparently compiled in the background while you are editing. |
Publishing Your Project
Click the Runtime → Build and Publish icon.
The Publish command creates a read-only protected version of a project that is suitable to be deployed in the field.
When the Publish command is executed, a new Project file (with the extension ".dbsln") is created with the version number selected. The Published Projects (with the extension ".dbrun") are similar to the current project and can be opened only in read-only mode. This provides you with a safe backup version of published applications.
| A project does not need to be published unless a read-only protected version of the file is warranted. Otherwise, the project file needs to be copied to the target computer. |
It is NOT necessary to publish the project to install it for production. If the project is expected to have continuous changes when in the field, it is easier to put the main project file (.dbsln) directly on the production computer.
The main benefit of publishing is that the system creates a compact and read-only version of the project file. The created file has the same name of the project's and it has the publish version number along with the ".dbrun" extension. This allows the system to comply with regulated industries.
The publish command is usually used in case you want to:
- Protect the project from modification. When deploy a read-only version of the project. For instance, to be in compliance with certified and regulated environments.
- Use the automatic version numbering system. The result of publishing is a ".dbrun" file that also contains a major (1.0) or minor (0.1) version number as part of the file name. In addition, Track Changes helps you manage the files published to the field, including which project build they are.
The ".trun" file is always read-only, but you can optionally hide the project configuration from the end-user as well. This is an independent option defined in the Security System. If you do not 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. |
Build and Pack Projects
The platform constantly compiles the module you edit in the background and validates all scripts and displays. If you have not run a full build, the BuildStatus column reflects any warnings or errors found during the background compile process.
If a row has a red X, double-click it to go to the source of the warning or error. Warnings are informational and do not stop the script from running. Errors prevent the specified script from running, but do not affect the whole application. Even if a script or display has a warning, it will still run.
Periodically, you should run a full build:
- When you have made many changes and you want a full validation and to recompile the whole project.
- When you want to assign a build number to a version.
- When you want to pack the database. When the build executes, the system creates a backup of the current project file. If you want to save the project as it was for the build, rename the backup file.
- When you are getting ready to publish, that is, create the read-only runtime application.
To build the application:
- Go to Runtime → Build and Publish.
- Configure the parameters according to your needs.
If you want to pack the database, select Pack database after build to significantly reduce the project file size. The system creates a file with the backup extension, which is the database before the application is packed. You may want to pack the database every time you run a build.If you want to save all displays, select Verify Symbols and save all Displays. Be sure to use this option if you have made changes to the symbol library. This option applies to all symbol library changes throughout the project.- Click Build.
When checked, a backup of the project that is connected with the build is automatically created. It is also possible to pack a project without building. To do this, click the Pack button. |
In this section: