S
slacroixak
Guest
Laura, I am not looking for yet another way to issue a message in an ABL log. We develop some .Net stuff that can be used *outisde* of the ABL world (at least when we test it in stand-alone mode, or when the ABL is not yet in the picture, or in some other cases...) Now, when something goes wrong with that .Net code in an ABL process, we would like to see those logs. So far, we can manage to redirect the standard output for a simple ABL batch process, but NOT for an AppServer, hence the request. On Friday, I entered a new Enhancement Request asking for a new log-entry-type to intercept the standard output and the error output. Perhaps we should also extend it to support standard logging mechanisms like log4net. The idea is to keep on single central smart log file (with variable config, rotation etc...) as opposed to deal painful multiple logs to configure, gather, correlate etc... (when you're happy to know about there existence) Does this make more sense to you now? That all being said, I like the ability of being able to send a message to the Error output with System.Console:Error:WriteLine() so a script that calls an ABL process has now the ability to get some details when something fails. In that case, we should quit an ABL session by calling the Environment.Exit( ) .Net method (I have not tested for an AppServer), that leads me to that missing bit I have been struggling for ages with the ABL: the ability to provide an optional exitCode for the native QUIT Statement.
Continue reading...
Continue reading...