
0
Fixed
Command line client always exits with zero
This happens with FixInsightCL version 2015.02upd1
I call the command line client from a NAnt script. The intention is to fail the build when a file can not be parsed by FixInsight.
For debugging purposes I currently capture the exit code in a result property and print it to the console.
I call the command line client from a NAnt script. The intention is to fail the build when a file can not be parsed by FixInsight.
For debugging purposes I currently capture the exit code in a result property and print it to the console.
- When I introduce a parser error in the .dpr file (e.g. insert '###' in any line), FixInsightCL reports "Failed to parse <file>.dpr", but still exits with zero. Would have expected exit code 1 or 2 here.
- When I introduce a parser error in any of the project files, Fixinsight writes "<file>.pas Fatal parser error" into the log file and exits with zero. Would have expected exit code 1 here.
Customer support service by UserEcho
This works fine for me. I just want to make sure that we are talking about the same problem.
How do you return the exit code? In my command line application (compiled with XE2) I return it the following way:
Which means I exit with zero in case of an exception... Have to fix that :)
FixInsightCL version 2015.02upd1.
There is no version Info shown in Windows explorer.