记录Powershell作业结果(Logging Powershell Job Results)

 我创建了一个基本上收集信息的PowerShell界面，然后通过Start-Job将该信息发送到外部PS脚本。 我有一个计时器，每秒都会触发接收作业，并使用我创建的作业中的STDOUT更新输出框。 
 
 外部PS脚本： 
 
 该脚本具有许多功能（利用许多cmdlet），并将通过Write-Verbose将消息打印到日志中。 问题是，有时在这些函数中我会打印消息和/或返回一个值。 
 
 众所周知，函数返回的任何内容都放置在标准输出中。 因此，只要函数返回一个值，该值就会打印到输出Rich Textbox控件中。 我不想那样。 此外，如果我正在使用VERBOSE，则消息不会被打印在控件中（但是，它正在打印到控制台） 
 
 我想要什么 ：只将消息打印到我的富文本框和我的日志文件中，流中没有函数返回值（除非它们是消息本身的一部分）。 
 
 注意 ：我正在将这个应用程序从VB.NET应用程序重写到Powershell Studio应用程序......并且我注意到之前这是通过使用类似的外部PowerShell脚本将STD输出流式传输到文本框中来完成的 - 除了该脚本正在使用WRITE-HOST。 这对我来说没有意义，因为写主机甚至不应该放入流中。 
 
 替代方法 ： 
 
 我有一个工作示例，让作业添加到日志本身，然后让UI运行Get-Content -tail 1 ...这将工作，除了我的一些消息将被打印在多行上，并且它不会像预期的那样拉一切。 如果有人有办法让我在任何时候都能在日志中获得任意数量的新行，请告诉我。 这可能比我目前的方法更容易。 

I have created a powershell interface which essentially collects information and then sends that info to an external PS script via Start-Job. I have a timer that triggers recieve-job every second, and updates an output box with STDOUT from the job I created.
 
External PS Script:
 
This script has many functions (which utilize many cmdlets), and will be printing messages via Write-Verbose to a log. The issue is, sometimes in these functions I print messages and/or also return a value.
 
As we all know, anything that a function returns is placed into standard output. So anytime a function returns a value, that value is printed into the Output Rich Textbox control. I don't want that. Also, if I am using VERBOSE, the message is not being printed in the control (however, it is being printed to the console)
 
What I want: Print only messages to my rich text box AND my log file, with no function return values in the stream (unless they are apart of a message itself).
 
Note: I am re-writing this application from a VB.NET app, to a Powershell Studio app... and I noticed previously this was being done by streaming STD Output into the text box, using a similar external powershell script--except that script was using WRITE-HOST. That doesn't make sense to me, as write-host isn't even supposed to be put into the stream.
 
Alternative Approach:
 
I had a working example of letting the Job add to the log itself, and then having the UI run Get-Content -tail 1... This WOULD WORK, except that some of my messages will be printed on more than one line, and it wouldn't pull everything as expected. If anyone has a way for me to get any X number of new lines in the log at all times, let me know. That might be easier than my current approach.

原文：https://stackoverflow.com/questions/40598414