I want to use CruiseControl.net as a service and have it launch the Fitnesse test runner as a task to run a bunch of acceptance tests using the watin fixture which starts IE. Oh and I want to do this all on a virtual server.
The above all works fine if I'm not running CC.Net as a service (ie. log in to the server via remote desktop and launch the CCNet.exe from the desktop).
I'm pretty sure just marking the CC.Net service as "allow interaction with desktop" won't be enough (it's a virtual server so there may not even be a winstation0). Though I haven't specificially tried this (in the past I tried running Fitnesse as a service and it couldn't start IE via the watin fixture... so I'm pretty confident that more that "allow interaction with desktop" will be needed).
I'm thinking I'll need a .exe that can create a winstation, log on as a specific user, and then launch IE (actually maybe just a shellexecute so I would not be limited to just ie).
Has anyone done anything similar in the past? Any specific pitfalls? Is this worth doing... or should I just do a remote desktop and then disconnect?
Note that the overall goal here is to have a reliable CC.Net process that invokes Fitnesse which in turn invokes IE.