Visual Build Pro 4

•	Existing projects created in Visual Build Pro 4 can be loaded by Visual Build 5+. The file schema has not changed, but if steps for new custom actions are added to the project or new features are utilized, projects saved in the new version may not build correctly in earlier versions.

•

The default location for application configuration files has changed. The default path for version 4 was the application installation path. For backward compatibility, if existing configuration files exist in the application installation directory, they will be copied to the new default path during installation. This change was made because not all users have the necessary rights to modify files in the installation path.

•	In version 4, the object model Macros.Load documentation was incorrect (the logic for the Clear parameter was backwards). In Version 5, the default has been changed from True to False to match the actual behavior of prior versions when a value was not passed.

•

The LOGFILE system macro, configured in Application options, is no longer automatically enclosed in double quotes. If the LOGFILE macro contains spaces and is passed as a command-line argument in a Run Program step, use the QUOTE_STR system macro to add quotes if necessary(i.e., %QUOTE_STR(%LOGFILE%)%.

•

Version 5 optimizes the size of project files when a step is edited by removing step properties that 1) match their default values and 2) the property default value is the default for that field type (unchecked for checkboxes, first item in a drop-down list combo, or an empty string for string fields). This will reduce the size of projects in most cases, but do not be alarmed if some properties are removed from a step after it has been edited and the project saved.

•	The Scripts tab has been removed from the project view. Scripts can still be accessed and managed from the Script Editor, which is available from View \| Other Windows \| Script Editor on the menu bar.

•	Macros are no longer allowed to contain spaces in the name. This was previously allowed, but an error would occur if the macro was referenced and expanded during a build. Existing projects with such macros can be loaded, but it is not allowed on new macros or when renaming existing macros.