We have had problems with tasks that hang, so we used the Asynchronous Action to have one action run the task, and another task wait for completion and kill the task if it does not complete withing a reasonable time.
The problem was thus solved untill we started to use FB in our CCNet (Welcome to CruiseControl.NET - Confluence) server - and sometimes two FB projects were kicked off simultaneously.
Since we had no way of finding the ProcessId of the task, our action would kill devenv.exe - but now we could have two instances of devenv.exe - and we do not know which one to kill.
Any plans for adding Action Timeout to the general action - and have that kill the action that did not complete?
Hi Espen,
Thanks for the suggestion. We actually already have Action Timeout on our list of enhancements :)
cheers,
tate.
That would be cool, however, is there any kind of workaround we can use in jscript? Start a thread that stops the action after a certain time or something similar?
Sorry, there’s no workaround to timeout an action.
But, FinalBuilder 5 now does have action timeouts for some actions. The option is available on the Runtime tab in the Timing section. (eg. have a look at the Compile VS.NET Solution action, or the Execute Program action). If there is an action that you use that doesn’t have the option and you need it, let us know and we’ll see if we can sneak the feature in 
hth.
.t8