The Build and Publish page provides commands for compiling solutions and creating deployment packages. Build validates scripts and displays, while Publish creates read-only production versions.

Access: Runtime → Build and Publish

Parent Page: Runtime Designer UI (Reference)



Build Operations


Build Process


The Build feature compiles displays and scripts for final verification:

OptionFunctionWhen to Use
BuildExecute compilationBefore deployment
Save BackupCreate .dbbak fileMajor changes
Rebuild AllComplete recompilationFull validation
Validate DisplaysCheck UI componentsDisplay changes


Build Settings

SettingOptionsPurpose
Temp FolderDesigner Settings / ProgramDataWorkspace management
Debug InformationInclude debug dataDevelopment troubleshooting


Temp Folder Locations


  • Designer Settings: SolutionPath\DesignerSettings\
  • ProgramData: \ProgramData\FrameworX\


When to Build


Build is automatic during development but manual build is useful for:

ScenarioPurpose
Many changes madeFull validation
Assign build numberVersion tracking
Pack databaseOptimize storage
Before publishingFinal verification


Build Process Steps


  1. Navigate to Runtime → Build and Publish
  2. Select Rebuild All and Validate Displays
  3. Click Build
  4. Review build results
  5. Fix any errors shown


Publish Operations


Publish Process


Creates read-only .dbrun file for production:

SettingFunctionResult
PublishCreate deployment fileSolutionName_Version.dbrun
VersionCurrent version numberAuto-incremented
Next IncrementVersion strategyMajor/Minor


Version Management

Increment TypeExampleUse Case
Major1.0 → 2.0New features, breaking changes
Minor1.0 → 1.1Bug fixes, small updates


Build Status


Background compilation provides continuous validation:

StatusIndicatorAction Required
Green?None
Warning??Review recommended
Error?Fix required

Double-click any row with issues to navigate to source.


Build vs Publish


Build Only


Suitable when:

  • Continuous development expected
  • Frequent field changes
  • Development environment
  • Testing iterations


Publish Required

Necessary for:

  • Regulated industries
  • Locked production systems
  • Version control
  • Read-only deployment


Validation Results


Warning Types


Warnings are informational:

  • Won't stop execution
  • May indicate potential issues
  • Should be reviewed


Error Types

Errors prevent execution:

  • Script won't run
  • Display won't load
  • Must be fixed


Best Practices


Development Phase

  • Use automatic background compilation
  • Fix errors as they appear
  • Don't build unnecessarily


Pre-Production

  1. Run full build with all options
  2. Fix all errors
  3. Review warnings
  4. Create backup


Production Deployment

  1. Final build and validation
  2. Set version number
  3. Publish solution
  4. Archive .dbrun file



File Types


ExtensionTypePurpose
.dbslnSolution fileDevelopment version
.dbbakBackup fileBuild backup
.dbrunPublished fileProduction deployment


Troubleshooting


IssueCauseSolution
Build failsScript errorsCheck error list
Publish disabledBuild errors existFix all errors first
Large file sizeNo compressionEnable database packing
Version conflictManual editUse version controls


See Also






In this section:

The root page V10:@parent could not be found in space v10.

  • No labels