coderanger.com blog news about what I am developing and other random thoughts
BuildIT 2.0 Build 121 Released
A new build is available that fixes a couple of bugs and adds some new features:
- Fixed bug so you can get version information from different language EXEs
- Modified so it will run a DOS Command task tool process from given search paths if a path is not given, also removed validation that exe exists so this can be done
- Added condition operators to specify how to compare the condition values (has equals, not equal, contains, not contain and is empty)
- Added ability to have macros in command line log paths
- Added current build file to log so its clearer what file the log is reporting on
Previous builds; Build 120:
- Added ability to specify a ‘condition’ on whether a task runs or not. This is a simple case insensitive comparison of the value of a specific macro. The task only runs if the value specified is exactly the same as the actual macro value
- Added a new system macro “SCRIPTSTART” which contains the string value of the date and time the script started in format “21 July 2007 13:21″ … this can be passed into a VBS CDate or a JS Date object constructor to create a script usable date
- Fixed bug with wrong value being saved into macro when running a DOS Command Tool Task
- Added ability to specify if the “Send Email” task should send as Plain Text or HTML, and also can specify the Importance of the email
- Added some more script functions for new email facilites:
## Sends a plain or HTML email to an already connected SMTP server with given importance. Importance can be: 0=Low; 1=Normal; 2=High
BOOL SendSMTPEmailExtra( String strTo, String strFrom, String strSubject, String strMessage, BOOL bSendAsHtml, short nImportance )## Sends a plain or HTML email with attachment to an already connected SMTP server with given importance. Importance can be: 0=Low; 1=Normal; 2=High
BOOL SendSMTPEmailExtraAttachment( String strTo, String strFrom, String strSubject, String strMessage, BOOL bSendAsHtml, short nImportance, String strAttachmentPath )
Build 119:
- Added ability to save return value of DOS Command Tool Task into a given macro for later use
- Modified command line version so it exits with appropriate exit code depending on if it finished successfully or not
- Modified output of file management tasks when operating on files due to date specifics
- Added some exception handling on scripts to try and catch failures due to security issues
- Added some more script functions:
## Returns whether given task is enabled or not. If task name doesn't exist, it returns FALSE
BOOL IsTaskNameEnabled( String strTaskName )## Returns whether given task has executed yet or not (current task would return false)
BOOL HasTaskNameRun( String strTaskName )## Returns whether given task has succeeded to execute or not (disabled tasks or current task would return false)
BOOL HasTaskNameSucceeded( String strTaskName )## Returns whether given task has failed to execute or not (disabled tasks or current task would return false)
BOOL HasTaskNameFailed( String strTaskName )## Returns the given named version field of a file with version information
String GetFileVersionString( String strFilePath, String strVersionStringName )## Returns an MD5 hashed string from given string
String ConvertToMD5( String strUnhashedIn )## Returns an SHA256 hashed string from given string
String ConvertToSHA256( String strUnhashedIn )
Build 118:
- Fixed same CPU bug in MSDev/VB Tasks
Build 117:
- Fixed major bug eating up all CPU when running a DOS command
- Fixed issue with double-clicking tickbox would edit task instead of not
- Fixed issue with file management dialogs would not size even though they had sizing grippers
- Added ability to use DEL and INSERT keys on files list in Manage Files task
- Fixed crash bug with incorrectly enabled edit/delete buttons when creating a Manage File tasks
- Fixed bug where encoded characters in XML File parameter values where not converted. This would mean that apostrophes in task names and other places would load back in as '
This entry was posted on Sunday, July 8th, 2007 at 10:16 pm and is filed under BuildIT, General.
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
August 1st, 2007 at 11:39 am
Hi,
Great tool you have created here. Do you have any plans to support Visual Studio 2005 solutions? The main difference with Visual Studio 7 / 2005 seems to be BuildIT can’t parse out the build configuration.
Thanks.
August 13th, 2007 at 12:30 am
Thanks for the new 124 Version, but what was changed?
Great tool anyway. Very cool. Good free.
Cheers, murphy
August 21st, 2007 at 10:03 pm
The last couple of updates were minor bug fixes caused by previous builds, not worthy of a full mention.
As for VS2005 solutions, it is supposed to work but only if you do not have VS.net also installed as the two products share the same registry key app locations (badly and wrongly).
What I might have to do is create separate task types for each version to get over these problems.
September 4th, 2007 at 6:05 pm
For VS2005, could you just have a selection on the task or even project level that tells if you’re using VS2003 vs VS2005? Or could it detect the project file format somehow and use that to tell it where to look for the compiler(s)?
I too would really like to be able to use this tool for both 2003 and 2005.