E. Crane Computing
E. Crane Computing                                                                                                                           Log In to Support Forum
What's New in PowerGen Version 6.5

Support for PowerBuilder V10.5
PowerGen Version 6.5 adds support for PowerBuilder V10.5, while continuing support for PB V5.x, 6.x, 7.x, 8.x, 9.x and 10.0. Existing project files and scripts are fully compatible with the new release.

Import and Export HEXASCII-encoded source files
New Import and Export options
Option to automatically detect the encoding
Command line parameters to specify encoding

Create Projects from Targets
New Projects can be created from an existing PB Target (.PBT) in the file system. This is in addition to Targets defined in the Registry.

Incremental Regeneration Improvements
Enhanced to show, in the output log, when an object is regenerated because its ancestor has been modified.

Most-Recently-Used Project Menu
The most-recently-used Project menu is widened to show more of the path to the Project.

Preserve case of PBL comments
When creating a PBL on the command line, PowerGen will preserve the case of the comment string.

Numerous bug fixes

  • Cancel function fixed in Build All operation, to skip all remaining processing
  • PBG files are now created when synchronizing a Project’s library list
  • PBG files are now created when Adding/Inserting PBL’s in a Project’s library list
  • When PowerGen created PBG files, the PBG’s will be created whether or not they are specified in the project.
  • Synchronize function would fail if Application object’s name had been modified to be case-different then when it was first created.
  • Optimize would fail on PB10 PBLs with very long comments
  • Errors not being reported for Import function
  • Project error file not being deleted in Bootstrap Import, if no errors
  • Optimize removing registration information (V7 and earlier PBLs)
  • Importing objects using PBG’s for a single PBL if the PBL was specified with a relative path
  • Corrected error reporting in regeneration when an object with errors is regenerated multiple times
  • Objects with long multi-line comments were failing regeneration. In some cases these long comments were caused by a problem in PB, where comments were growing as a consequence of adding the object to source control.
  • Objects with HEXASCII encoded characters in comments were not being imported correctly.
  • Objects with leading underscores in their names were not importing into PB10.
  • Objects with OLE were not copied correctly in PB10.0 and later.
  • Sharing violation running on a network drive.