Orchestrations in BizTalk Server 2004 may have call dependencies between them which mean that they must be started and stopped in a specific order.
I've written an orchestration dependency lister (available here, on Got Dot Net), which examines a server and produces an XML file detailing the order in which its deployed orchestrations must be started.
Included in the zip file are two XSL files to transform the output from the Orchestration Dependency Lister into DOS batch files to start and stop all orchestrations. I'm sure you can come up with more creative uses of this, such as integrating it with Scott Colestock's NAnt script (I've done this myself, but only for the old version of his script)
Finally, a Nant file is also included to first call the Orchestration Dependency Lister, and then pass the output through the two XSL files to show how you would include it in a continuous build process.
I'd be interested to hear your feedback...