From: Chris F. <Chr...@ca...> - 2011-11-03 20:18:46
|
Can you mimic how your GUIs (run button) call the Nant processes, and start off Nant from a command line window the way they do? Or if you have the code that starts the console window, put a cin <<; statement, which will freeze the window until you hit <CR> in it. -chris From: Macdiarmid, James D. [mailto:JAM...@sa...] Sent: Thursday, November 03, 2011 12:37 PM To: nan...@li... Subject: [NAnt-users] Need help with a NAnt internal error Hi all, I have a C# Win Forms application that we use to kick off our build process. This application launches a form which has several text fields which we use to pass file path information to properties in our script, and a run button. The run button starts a windows console process to call the Nant executable and pass the form data on the command-line. Whenever I kick off the build process this way I am getting a Nant Internal error in the console window however I can't read all of it. As soon as the script is done the console window closes. Is there any way I can keep this process open or log the errors? I know nant has a command-line parameter for sending information to a log file which I am passing already on the command-line however the internal error is happening before it can log anything. Please help - this is making me crazy and I think I'm on my last hair follicle. Lol Thanks, Jim ***This e-mail message is intended only for the above named recipient(s) and may contain information that is sensitive or proprietary. If you have received this message in error or are not the named recipient(s), please immediately notify the sender, delete this e-mail message without making a copy and do not disclose or relay this e-mail message to anyone.*** |