An alternative is to run your executable via psexec using the -i switch (interact with the desktop). For example:
psexec.exe -i 0 your.exe This should enable your GUI executable to run, even when running CCNet as a service. http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx Regards, Alex Roebuck. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of seffyroff Sent: Friday, August 29, 2008 4:27 PM To: ccnet-user Subject: [ccnet-user] Re: Executable Task Block Exec Environment Different Somehow? That's acceptable to me. One of these days I'll have the words 'Quick and dirty' mounted on a plaque above my desk. Thanks for the help! On Aug 29, 3:57 pm, Daniel Hommel <[EMAIL PROTECTED]> wrote: > seffyroff writes: > > What are the downsides to not running as a service? > > Your "cruisecontrol user" needs to be logged in and have the console > runner running. That's not very elegant on a server. But as far as i can > tell it works quite well.
