Overview
As you do the Solution Configuration, the system automatically compile Scripts and Displays, with no user intervention.
Is specific situations, like preparing the solution for Deployment, or creating a solution backup, or just willing to have a deeper validation, this page provides the following optional commands:
Build: compile and verify Scripts and Displays, apply a Build Number to facilitate version control.
Publish: 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 phasecopy of the Solution for deployment in controlled areas.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Build
the Build FeatureThe Build feature compiles all projectthe solution's displays and scripts for final verification before deploying the project for production . Build provides complete deployment. It ensures thorough verification of an the application's scripts and components as part of the preparation for production.
Build compiles all the solution's displays and scripts, providing a final check before deploying the application into production. During development, this process is not necessary as when preparing it for final production. However, this is not necessary during the development stage since all project modifications are automatically and transparently compiled compiled in the background while a project is edited. editing the solution.
The section Build and Publish is presented on detailed in the following image.
| Index | Description |
|---|---|
1 | Build button -, The Build command does not need to be executed after a projectsolution is edited as it happens automatically in the background. The Build command only needs to be used as a final verification before a projectsolution 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 solution. |
4 | Checking this box will make sure debug information is included. |
5 | Publish button create an only read version of this projectsolution, with the next configured version. |
6 | Option used for managing solution versions. |
7 | Option used for managing solution versions. |
8 | This table shows the current status of each script and display potential errors or warnings. |
History - The historical Builds and publishes is available in Solution/History. shows the number of times you executed a whole build for this project.
| Note |
|---|
Executing a Build is useful for achieving complete verification of an application's logic when an applicationit is being prepared for final production, but it is not necessary during the development process. Any modifications you make on a projectsolution are automatically and transparently compiled in the background while you are editing. |
A project's configuration is saved in a file with the extension "dbsln". Using the Publish procedure that is described in next section, you can create read-only versions of the project for runtime execution only. This version will have the extension ".dbrun".
Publish
The Publish command generates a read-only protected version of a solution ready for field deployment. This command produces a new Solution file (".dbsln") with the chosen version number. The Published Solutions (".dbrun") mirror the current solution but are accessible only in read-only mode, offering a secure backup of published applications.
Click the Runtime
Publishing Your Project
Click the Runtime → Build andPublish icon.
The Publish command creates a read-only protected version of a project solution that is suitable to be deployed in the field.
When the Publish command is executed, a new Project Solution file (with the extension ".dbsln") is created with the version number selected. The Published Projects Solutions (with the extension ".dbrun") are similar to the current project solution and can be opened only in read-only mode. This provides you with a safe backup version of published applications.
| Note |
|---|
A projectsolution does not need to be published unless a read-only protected version of the file is warranted. Otherwise, the projectfile needs to be copied to the target computer. |
Click the Track Changes:
UseCount: Shows how many times each object is used inside the application, along with a reference to the object.
CrossReference: Shows where each object is used and shows a list of unused objects. You can double-click on a selected reference in order to jump to its location.
It is NOT necessary to publish the solution to install it for production. If the solution is expected to have continuous changes when in the field, it is easier to put the main 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 solution file. The created file has the same name of the solution and it has the publish version number along with the ".dbrun" extension. This allows the system to comply with regulated industries.
The publish commandis usually used in case you want to:
Protect the solution from modification. When deploy a read-only version of the solution. 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 solution build they are.
| Info |
|---|
The ".trun" file is always read-only, but you can optionally hide the solution 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 configuration, remove the permission of the GUEST user and other users to edit the solution before publishing it. |
Pack
Build and Pack ProjectsThe 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
projectsolution.
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
projectsolution file. If you want to save the
projectsolution 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 andPublish.
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.
Configure the parameters according to your needs.
Click Build.
| Info |
|---|
When checked, a backup of the project solution that is connected with the build is automatically created. It is also possible to pack a project solution without building. To do this, click the Pack button. |
Project Version Control
Tracking configuration changesOur platform provides many ways to help you track the project configuration changes:
In
order to enable or disable this, you must be logged in as an Administrator. By default, object tracking is only enabled after you publish the project, but you can enable it anytime.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. If the project is expected to have continuous changes when in the field, it is easier to put the main project file (tproj) 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 ".trun" extension. This allows the system to comply with regulated industries.
The publish commandis usually used in case you want to: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 ".teng" 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.
- Have 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.
- Protect the project from modification.
| Info |
|---|
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. |
To publish the project:
- Go to Runtime → Build and Publish.
- Select the desired build settings and Click Build.
- Go to Runtime → Build and Publish. The Current Project Settings fields show the read-only status of the project.
- Select the Publish Settings you want.
- Click Publish.
this section:
| Page Tree | ||||
|---|---|---|---|---|
|