[Progress Communities] [Progress OpenEdge ABL] Add a new LOG-ENTRY-TYPE to intercept and log Standard output (System.Console.Write*) and Error Output

  • Thread starter Thread starter slacroixak
  • Start date Start date
Status
Not open for further replies.
S

slacroixak

Guest
As discussed on the forum recently. Nowadays, .Net code invoked from the ABL can output things to the Standard output or the Error Output (see the example below). It would be very useful to intercept these pseudo log activities with the log-manager to keep dealing with one single unified log, especially to trouble shoot issues in GUI interactive sessions or AppServer sessions /* scratch.p */ MESSAGE "poney alert-box message" VIEW-AS ALERT-BOX. System.Console:WriteLine("poney Standard output WriteLine()"). System.Console:Error:WriteLine("poney Error output WriteLine()") . pro -b -p scratch.p or prowin32 -b -p scratch.p >stsout.log 2>errorout.log We may also want to extend the LOG-MANAGER capabilities to intercept log4net log activities as well. Note, that in C#, it is possible to intercept Console output as explained below: Is it possible to intercept Console output?

Continue reading...
 
Status
Not open for further replies.
Back
Top