Version 4.0.124 (.Net)

• Bug Fix – On changing the AssemblyName and building a spurious error was being reported regarding location of the build output.
  
• Bug Fix – Changed handling of some VB.Net build config values as they are processed differently by the compiler than other .Net languages.
  
• Bug Fix – When building an object that has defaulted to the 'debug' build config as it's custom build config isn't present a spurious error was raised.
  
• Bug Fix – When projects contain references to other projects the build would fail. Build Manager now updates the project to point to the assembly prior to building and then restores the project reference post build. This is for .Net 2002 & 2003. Project references in 2005 compile as expected as the compiler looks for the assembly for you.

Version 3.2.35

·         Fixed Bug – Minor bug fixes. Ensured BuildProcessFinished event executes even when no projects are built.

Version 3.2.27

·         Enhancement – Added a reference to our internal Projects collection to all Script events. This will allow us to more easily customize scripts for you. We have not documented the available properties as they may change without warning in future versions.

·         Enhancement – Added a script that allows you to set the version numbering for each project to match that of a selected master project.

·         Enhancement – Added the ability to easily get/save to the registry via scripting. These are the same as the VB commands. To call from a script use oCommon.G7xGetSetting and oCommon.G7xSaveSetting. These take exactly the same parameters as the VB equivalents.

·         Fixed Bug – When running a SourceSafe label command and a build had not been run the label would not be updated. This would only occur where a label script was being used.

Version 3.2.22

·         Fixed Bug – If certain conditions were met the SourceSafe GetLatest task would recursively get the latest version of code even when ‘Get Recursive’ is set to False.

·         Fixed Bug – Regression. The Minor Version of ActiveX GUID’s was not being converted to hex prior to testing for version changes. This could cause incorrect build order from being displayed. This would only occur for References(DLL’s) not Objects(OCX’s).

·         Fixed Bug – When a PreAnalyse task failed this would not halt further tasks from running in unattended mode.

·         Fixed Bug – The Label script for SourceSafe was creating a label using the RevisionVer post-build instead of pre-build.

Version 3.2.20

·         Enhancement – Option to check for NewSourceCode without having to refresh the workspace.

·         Enhancement – Open Project Groups from the Project Selection screen.

·         Fixed Bug – Possible recursion could occur when 1^st opening a workspace or creating a new one.

·         Fixed Bug – BuildProcessFinished build tasks failing to run. Inadequate error reporting in place.

·         Fixed Bug – When running a build the BuildProcessFinished task would not run if ‘Success Only’ was selected and there were projects that had failed being built and are unselected.

·         Fixed Bug – Internal issues relating to the implementation of SourceCode control and to how Invalid References were determined and fixed.

·         Fixed Bug – The Label SourceCode Script has been updated to correctly return the created Label.

Version 3.2.0

·         Enhancement – Full integration with NuMega TrueCoverage and TrueTime. You can now build using TrueCoverage & TrueTime allowing you to add Numega debugging/profiling functionality at build time to all the selected projects. (Requires NuMega DevPartner 6.5 for Visual Basic).

·         Enhancement – Full integration with NuMega FailSafe. You can now add FailSafe instrumentation to selected projects at build time. You also have the ability to remove instrumentation as well. (Requires NuMega DevPartner 6.5 for Visual Basic).

·         Enhancement – When new projects to a workspace are found and displayed you can now ‘Select All’ or ‘DeSelect All’ via a popup menu. (Right mouse click).

·         Enhancement – The build process can be started from anywhere using CTRL+F5. You no longer have to wait for the Hierarchy to be determined before being able to begin the process.

·         Enhancement – VB Script. You can now clear the log by using the following syntax: oCommon.ClearLog

·         Enhancement – The order of the build log can now be set via the registry. This allows having the log either in an ascending or descending list. Merge the registry files found in c:\program files\g7x build manager\customize to suit which way you wish to view the build log, Ascending or Descending.

·         Enhancement – The Scripted Label functionality exposed for the VSS label task now includes the same properties exposed in normal VB Script tasks and events. The same Script editor used for VB Scripted tasks is also exposed as the editor for the Scripted Label.

·         Enhancement – Modifications made to the scripting engine now allow for writing code directly in the Visual Basic IDE. This requires instantiating an ActiveX exe created by G7x. Full source code is provided to allow you to code all your customisations directly in VB.

·         Fixed bug – On certain machines the way Build Manager interacted with the Registry could cause references to be shown as invalid when in fact they were valid. Thanks to Allan Nielsen for assisting G7x with this issue.

·         Fixed bug – The Output file for Unattended builds would not change from the default value of ‘app path\unattended.txt’. This now works as expected.

·         Enhancement – DLL Base Addresses can now be edited via the Project Properties dialog or with VB Scripting.

·         Enhancement – A DLL Base Address dialog is now provided to automatically re-base addresses for all selected projects. CTRL+D to open or from menu Tools | Set DLL Base Addresses.

·         Enhancement – The VSS DatabaseName, Username & Password are now exposed to VB Scripted tasks. Syntax: oCommon.VssDatabase, oCommon.VssUsername and oCommon.VssPassword. These values will return empty strings unless a valid connection to Vss has been established.

·         Enhancement – When Circular References were detected in the past the detail was not being displayed to the user. This now raises an error that you can flag to stop the build on.

·         Fixed bug – When attempting to CheckOut via VSS and the file is check out by another user and the file is the first project to be checked out an internal error would be raised instead of notification that the file was checked out by another user.

·         Enhancement – When attempting to GetLatest or CheckOut Projects/Files from SourceSafe and the User doesn’t have rights an internal error message would be displayed. We now trap this condition and have supplied a flag on the SourceSafe options screen to allow you to fail the task or not when this condition is encountered.

·         Enhancement – When prompting a user to enter SourceSafe login details they had to manually search for the srcsafe.ini file. There is now a combo box listing all registered VSS databases for easier selection.

·         Optimisation – When selecting sub projects in the Get Latest dialog Build Manager was automatically retrieving all related labels for the selected projects whether you had the ‘Get By Label’ option selected or not. Build Manager will now only populate the list of available labels if you have ‘Get By Label’ selected.

·         Enhancement – Under the BuildProcessFinished event in a Scripted task only the projects that had been built were included in the oProjects colletion. All projects are now included in this event. A new flag has been added to the G7x_BR enum.
G7x_BR_Success = 0
G7x_BR_Failed = 1
G7x_BR_NotBuilt = 2

Version 3.1.22

·         Fixed bug – When any VSS task is run at Pre-Analyse an error would be reported in the following procedure: G7SourceSafe.zCheckVbpAttributes. This error could be safely ignored and is now fixed.

·         Enhancement – Added ‘ResolvedCompatibleEXE32’ as a property under VB Scripting. This property points to the fully resolved path of the Compatible version file.

·         Fixed bug – When reading in the XML workspace all values are returned as string data types. On some non-english operating systems and input locales VB’s automatic datatype conversions would not work. We explicitly type all data extracted from the workspace now.

·         Fixed bug – When setting up a VSS task and no ‘Working Folder’ is set it could cause errors if the user did not enter the localspec. The user is now warned that a valid value must exist.

·         Fixed bug – Some users were unable to display the ‘Resolve Missing References’ dialog without encountering severe errors. This was due to quite heavy processing causing VB to lose an internal reference to a collection object. The processing has now been broken into more manageable chunks.

·         Fixed bug – If a fatal error was encountered while parsing a VBP the file was being left in an open state. The file is now closed if any error is encountered.

·         Enhancement – Added the ability to add your own text to the build log via scripted tasks.

·         Enhancement – Added the ability to shell commands via scripted tasks and wait for them to complete before control returns to the script.

·         Enhancement – Added the ability to flag a project not to be built in a scripted task.

·         Fixed bug – When ‘Resolving Missing References’ the VBP file could be updated even if is was read-only. VBP’s can now only be updated if they are writeable.

·         Fixed bug – SourceSafe. When a file is shared between 2 or more projects the 1^st instance found to be checked out was always checked in. The checked out file is now checked against which project it was checked out to before checking in. This now imitates SourceSafe’s behaviour correctly.

·         Enhancement – Under SearchCriteria there are now checkboxes in the listview control allowing easier removal/inclusion of VBP’s from workspaces.

Version 3.1.1

·         Enhancement – All common Project Properties are now editable under the VB Scripting task. This gives the developer even greater power in customizing the build process.

·         Enhancement – Build Configuration flags of Debug/Release have been added to bring Build Manager into line with Visual Studio Installer and Visual Studio.net. These flags can be set either as commandline arguments or within the BM IDE. This gives the developer the ability to code multiple decisions into VB Script tasks. For example: If the ‘Debug’ flag is set you could have a VB Script task changing project properties such as ‘SymbolicDebugInfo’= True and for ‘Release’ flag setting to False.

·         Enhancement – VB Scripts can now be added to the Build Tasks menu. This allows you to have your frequently used scripts a click away and new scripts downloaded from G7x will immediately available as a build task. 8 new Scripts are included with this release.

1 – Break Compatibility & Restore – Allows Build Manager to downgrade version compatibility to cope with frequent interface changes. Build Manager will then restore the original compatibility settings.

2 – Create Registration Batch Files – Creates batch files to register and Unregister all your ActiveX components.

3 – Debug Options (Set/Restore) – Using the Build Configuration flag allows a developer to set different Project Properties at build time based on whether the build is a ‘Debug’ or ‘Release’ build. I.e. Build config is ‘Debug’ so set ‘Create Symbolic Debug Info’ on to allow debugging of VB executables via C++ at runtime.

4 – Email Build Result (Outlook) – Emails the results of a build via Outlook

5 – Email Build Result (CDO/SMTP) – Emails the results of a build via Collaboration Data Objects. You must have SMTP installed and configured to use this script.

6 – Move to Staging Area – Moves all the newly built objects to a folder of your choice. Ideal for moving to a shared network location for developers/testers to get the latest build. Works well with the ‘Create Registration Batch Files’ script.

7 – Version Comments Maintenance – Ensure every time you build a project that the Product Name, Comments, & Legal Trademarks etc are set correctly for every project prior to building.

8 – Version Numbering Maintenance – Ensure every time you build a project it is using your products version numbering. I.e. Ver 2.5.0 with AutoIncrement turned on.
nb: Scripts 7 & 8 are easily modifiable to maintain any common Project Properties.

·         Enhancement – The ‘PostBuildProject’ task now has a flag ‘oProperties(“RebuildProject”)’ to specify a project should be rebuilt if it fails. This allows the ‘BreakCompatibility’ script to run. For example: A Project is built but fails as it is using binary compatibility. Using VB Script you can downgrade the compatibility to Project and then request Build Manager to retry the build. If successful you can then reapply binary compatibility. Build Manager will only allow 3 retries on the same project to ensure the build process doesn’t get caught in an infinite loop.

·         Enhancement – Added registry entry to allow non-English VB Developers to specify localised text to indicate a successful compile. Initial support for German VB. Thanks to Markus Schwaiger for help on this.

·         Fixed bug – Editing the ‘Advanced Optimizations’ on the Project Properties dialog was not indicating changes had been made. This could lead to settings not being saved.

·         Fixed bug – When building a Project and it needed to update dependent VBP’s it would make Read-Only VBP’s writeable. There is now a flag under ‘Build Options’ to determine whether to fail a build if a VBP is read-only. Default = On. To check for this error code in unattended builds the exitcode is 188.

·         Fixed bug – Project Properties can no longer be edited when a VBP is read-only.

·         Fixed bug – When a VBP’s file attributes change Build Manager now intercepts this and makes appropriate changes. I.e. Check-Out files changes file attributes.

·         Fixed bug – When running SourceSafe commands set up as Build Tasks via the ‘Run Now’ command on the context menu an unhandled error would occur if an error occurred in the VSS task. I.e. CheckOut and another user has a file you require would cause this error.

·         Fixed bug – When changing workspaces the Up/Down options of Build Tasks would not be reset to the correct state. This could cause an error when then moving tasks within the new workspace.

·         Fixed bug – After changing the order of ‘Build Tasks’ the execution order would still be incorrect in some situations.

·         Fixed bug – When ‘Resolving References’ and a corrupt key was encountered in the registry the error would not be reported and the list of valid references would not be populated. An error is now raised and the valid references list will populate.

·         Fixed bug – When parsing our XML workspace file and evaluating values being returned we would get Type Mismatch errors if the input locale is set to Norwegian. By explicitly type casting the returning XML data the issue is resolved.

·         Fixed bug – Compatible files located on network shares i.e. \\MyServer\Directory\MyBinCompat.dll were incorrectly being listed as missing when they were in fact present.

·         Fixed bug – When the ‘Unattended Execution’ flag was checked on Project Properties for an ActiveX Dll the ‘Retained in Memory’ checkbox was not being enabled/disabled as needed.

Version 3.0.2

·         Fixed bug – The ExeName32 property under VB Scripting did not contain the path to the executable as well. ProjectPath has also been added to all scripts.

·         Fixed bug – When changing project properties (and not implicitly saving the changes) and selecting ‘2. Build Projects’ any changes made were being ignored.

·         Fixed bug – Fixing tabbing on VB Script dialog so Tabbing will work as expected in code window.

·         Fixed bug – When attempting to exclude a project via the Project Selection dialog and ‘View Project Properties’ was set to anything other than ‘Default Detail’ the VBP would not be excluded.

·         Enhancement – Build Tasks can now be moved up & down.

Version 3.0.0

Build Tasks interface added. Allows addition of custom tasks to be performed before, during and after the Build Process. The following custom tasks are now available:

1.       Visual SourceSafe Integration.
Get Latest / By Label
Check Out - By Filemasks i.e. ‘*.vbp’
Check In - By Filemasks and ability to Label
Undo Check Out - By Filemasks
Label – Apply labels on a Project or File level
Label – Labels can be created using VBScript

2.       VB Script Integration.
Execute VB Script and access Project Properties exposed by the Build Manager.
Ability to import pre-built scripts allowing easy extensibility of the Build Manager.

3.       Execute Applications.
Run any application you want. Build Manager checks for returns code so you can flag whether your task was successful or failed.

Bug Fixes / Enhancements

·         Fixed bug - Path not found error occurred when checking for a compatible file and the directory was missing.

·         Enhancement – Unattended Build Flag ‘Fail On No Exe or Compatible file’ has been split into 2 distinct flags. ‘FailOnNoExe’ which will return error code 196 and ‘FailOnNoCompatible’ which will return error code 192 if encountered.

·         Fixed bug – The Output file for Unattended builds would not change for the default value of ‘app path\unattended.txt’. This can now be changed.

·         Enhancement – Added 3 new exit codes to signify failure of Build Tasks. See Build.bat in app install directory for full details.

·         Enhancement – The build log is no longer automatically cleared when building starts. The log now has a ‘Clear log’ button for manual clearance.

·         Enhancement – Added association to G7x workspaces. By right mouse clicking on a .G7ws file you will be able to either ‘Open’ the workspace or ‘Build Now’ which will start the build process. Default action is ‘Open’

Version 2.5.0

·         Major Enhancement – Build Manager now exposed as an object library. This will allow you to customise your Build Process in anyway you like. See the Programmers Reference in the help file for full details.

·         Fixed bug – Workspace would not save when no projects were selected

·         Fixed bug – User not prompted to save changes to the current workspace when opening an existing workspace or creating a new workspace.

·         Request – Confirmations dialog option: ‘Update Dependent VBPs with new GUIDs’ flag and ‘Stop Building / Compiling if Error encountered’ flag now saved to the workspace instead of the registry.

·         Enhancement – The 4 most recently used workspaces now included on the File menu.

·         Fixed bug – When VBP has reference to another VBP and the VBP is of type ActiveX Exe the Build Manager was not automatically fixing this invalid reference.

·         Fixed bug – It certain conditions source files, executables & compatible files would be shown as missing when in fact they were present.

·         Fixed bug – In the case where a developer had set the System or Hidden attributes on a VBP the Build Manager was unable to update the VBP.

·         Request – Registry settings are now saved to HKEY_Local_Machine instead of HKEY_Current_User.

·         Request – If a project is missing it’s executable file you can now flag it to be of type ‘NewSource’ so the exe is rebuilt. This is NOT the case for missing compatible files.

·         Fixed bug – Issue where projects listed in the 1^st level of the build hierarchy to be built would be missed out. (Thanks to Dean T for helping us with this one)

Version 2.00.022

·         Enhancement – Can now flag whether to continue building when a build error is encountered.

·         Fixed bug – When changes are made to a project via Project Properties and a Build process is initiated the user wasn’t being prompted to save their changes.

·         Fixed bug – Circular References. Bug where Build Manager would crash displaying a circular reference.

Version 2.00.020

·         Enhancement – Command Line processing included. Automate your Build Process.

·         Enhancement – Selected Projects are now saved with the workspace.

·         Fixed bug – ‘Select New Source’ now selects all projects with source code newer than the projects executable. This was not working when 1^st opening a workspace.

Version 2.00.008

·         Fixed bug – When selecting ‘exclude folders’ on the pupup menu of ‘Search Criteria’ the selected file was automatically being excluded.

·         Fixed bug – Popup Forms would always display on the Master monitor of a DualHead display even when then Build Manager was displayed in the secondary monitor.

·         Fixed bug – If a particularly corrupt VBP file was parsed it would halt the initialisation of Build Manager. We now continue on and warn the user of the InValid VBP.

·         Enhancement – Shortcut keys added by request

·         Fixed bug – Require Licence Key saving incorrectly

BETA Version 1.00.212 – Enhancements over Version 1.00

·         Search Criteria added. Allows user to include/exclude multiple paths, filemasks & specific files in the search for VBP and related files.

·         Support for ASP & HTM files containing Visual Basic ActiveX controls. Will now update internal references to CoClasses within ASP & HTML files in the event of the CoClass GUID changing on compile. Stops this error occurring when loading Asp/HTML pages: ‘An object has failed to load. The object will be displayed as text.’

·         Workspace concept introduced. Allows search criteria and default settings for VBP's to be stored. Easier to maintain multiple Projects.

·         Start-up dialog - Users now prompted to with a start-up dialog allowing them to open existing/recent workspaces or create a new workspace based on existing templates i.e. Visual Basic Projects Only or VBP's & Interdev Projects

·         Visual Basic Projects that contain ‘MISSING References’ are now highlighted/bolded so user can tell at a glance something is amiss.

·         Status bar now informs user of what task is being performed. Percentage bar added.

·         Ability to select only those Projects, which have source code that is newer than the Executable on loading of Workspace.

·         Filename/Executable to be built now displayed on the Compile Tab of Project Properties

·         ‘Display Legend’ added to Build Order. Displays info on what icons represent within the Build Order.

·         View Project properties in selection window – Allows Users to see all the Project Properties for all available Projects. Let’s you see at a glance whether values don’t match across the entire collection of Projects.

·         Resolve References – User now had option to resolve ‘Missing References’ for the currently selected Project or to resolve all missing references.

·         When opening a workspace the user is now informed if the Search Criteria finds new projects and allows user to include/exclude.

·         Fixed bug – Would only check certain source files to see if executable was out of date. We now check all.

·         Fixed bug – Missing source code was being alerted to user.

Version 1.00.143