Does Final Builder 5 resolve the issue with log file locking that was introduced with Final Builder 4?
To recap, the issue is with attempting to run more than one FB session of the same project file, usually with different parameters. In my case, it’s a scheduled build in the background and a foreground build conflicting.
When this happend in FB3, it used to let the build succeed by logging to a temporary file and discarding the log, whereas FB4 changed that to fail the build.
Vince talked about fixing this in a later release, is FB5 that release?
Regards,
Paul.
Hi Paul,
There is a new way around this problem in FinalBuilder 5, which is that FinalBuilder (both the IDE and the command line version) now support a /O or /OF option on the command line. If running a scheduled build with /O or /OF, the new FinalBuilder instance will close any other FinalBuilder instances which have the same project open.
/O will only close idle instances (ie not running) with no unsaved changes.
/OF (F is for Force) will close any instances, terminating the build and/or losing unsaved changes if necessary.
If this option doesn’t help, then the /TL option is still available for logging to a temporary log file.
All of these options are documented in the “IDE Command Line Interface” and “Command Line Version” help topics. /O is enabled by default in new schedules created within FinalBuilder, although existing schedules will need to be edited.
Hope this helps.
Regards,
Angus
And here’s the online links to the command line help:
IDE:
https://www.finalbuilder.com/finalbuilder/Help/HTML/commandlineinterface.htm
FBCMD:
https://www.finalbuilder.com/finalbuilder/Help/HTML/fbcmd.htm