Navigation: Introduction > Upgrading from Older Versions >
Upgrading from Visual Build Pro 6
|
Navigation: Introduction > Upgrading from Older Versions > Upgrading from Visual Build Pro 6 |
|
| • | Existing projects created in Visual Build Pro 6 (and earlier versions) can be loaded by Visual Build 7. The file schema has changed, so projects saved in the new version will not load or build correctly in earlier versions. |
| • | Visual Build Pro version 7 can be installed side-by-side with previous versions. The default installation path is C:\Program Files\VisBuildPro7 or C:\Program Files (x86)\VisBuildPro7 (on 64-bit Windows) rather than C:\Program Files\VisBuildPro6. Scheduled tasks, command (.cmd) scripts, batch (.bat) files, and Windows shortcuts that specify a full path for launching Visual Build will need to be adjusted for the new installation path (operations that do not specify a path [i.e., start VisBuildPro, double-clicking a .bld file, etc.] will launch the most recently installed version of Visual Build Pro). |
| • | The default application data folder is C:\Documents and Settings\All Users\Application Data\Kinook Software\Visual Build Professional 7 rather than C:\Documents and Settings\All Users\Application Data\Kinook Software\Visual Build Professional 6. During installation, any configuration files in the version 4/5/6 application data folder or install path will be copied to the version 7 folder. Also, the registry key to override the default application data path is HKEY_LOCAL_MACHINE\Software\Kinook Software\Visual Build Professional 7\ConfigFilesPath rather than HKEY_LOCAL_MACHINE\Software\Kinook Software\Visual Build Professional 6\ConfigFilesPath. |
| • | ListFiles.vbs from earlier versions is no longer installed in the TOOLSDIR. Use the List Files action instead or copy it from an earlier version. |
| • | The following obsolete global macros will be copied from an earlier installation but are no longer automatically created. Replace their use with an equivalent built-in action or create and initialize as appropriate if needed on a clean install. |
Macro |
v7 Equivalent |
Macro Value |
Parameters |
ATTRIB |
%DOSCMD% attrib FLAGS "FILENAME" |
FILENAME, FLAGS |
|
BCB |
"%BCBDIR%\Bin\BCC32.exe" |
||
BCBDIR |
C:\Program Files\Borland\CBuilder5 |
||
BJB |
"%BJBDIR%\Bin\JBuilder.exe" -build |
||
BJBDIR |
C:\JBuilderX |
||
CS_NET |
"%DOTNET_DIR%\csc.exe" |
||
DELPHI |
"%DELPHIDIR%\Bin\DCC32.exe" |
||
DELPHIDIR |
C:\Program Files\Borland\BDS\4.0\ |
||
DEVENV_NET |
"%DEVSTUDIO_NET_DIR%\Common7\IDE\devenv.com" |
||
REGEDIT |
RegEdit /s "FILENAME" |
FILENAME |
|
VB_NET |
"%DOTNET_DIR%\vbc.exe" |
| • | All Run Program-derived actions have been enhanced with Advanced and Remote tabs. The Log the command-line used option (typically on the Options tab in earlier versions) has been moved to the Advanced tab. |
| • | All Visual Build COM components, type libraries, ProgIDs, and interface GUIDs are different in version 7. User action components will need to be updated to reference the Visual Build Professional 7 Server type library and recompiled in order to work with version 7. Script code that uses ProgIDs of "VisBuildSvr6.Application" and/or "VisBuildSvr6.Builder" will need to be modified to use "VisBuildSvr7.Application" and/or "VisBuildSvr7.Builder" instead. |
| • | Actions are now registered under HKEY_LOCAL_MACHINE\Software\Kinook Software\Visual Build Professional 7\Actions rather than HKEY_LOCAL_MACHINE\Software\Kinook Software\Visual Build Professional\Actions. The COM Register action in version 7 registers actions at this location. |
| • | Custom logging components are now registered under HKEY_LOCAL_MACHINE\Software\Kinook Software\Visual Build Professional 7\Logging rather than HKEY_LOCAL_MACHINE\Software\Kinook Software\Visual Build Professional 6\Logging. |