cfexecute weirdness
I ran across an interesting "quirk" using CFexecute today...
When I run this code:
<cfexecute name="c:\windows\system32\tree.com" arguments="/?" variable="bar" />
<cfdump var="#bar#" />
<cfdump var="#bar#" />
...I get the error that "variable 'bar' is undefined".
...however if I use the "outputfile" attribute instead of "variable", I do indeed get the results I want.
After some discussion on the BACFUG list, it seems that the "timeout" attribute is required:
<cfexecute name="c:\windows\system32\tree.com" arguments="/?" timeout="20" variable="bar" />
...but if I don't include it, CF will happily compile and run the code, even if it's not able to populate my variable properly. :)
Quote:
timeout
Optional
0
Length of time, in seconds, that ColdFusion waits for output from the spawned program.
0: equivalent to nonblocking mode.
A very high value: equivalent to blocking mode.
If the value is 0:
ColdFusion starts a process and returns immediately. ColdFusion may return control to the calling page before any program output displays. To ensure that program output displays, set the value to 2 or higher.
If the outputFile attribute is not specified, any program output is discarded
Thanks for the clarification.