blocks|key|3069722|text|您可以在您的场景中使用其中的任何一个，因为它们会写入缺省流(输出和错误)。如果您将输出通过管道传输到另一个命令小程序，您可能希望使用Write-Output，它最终将在Write-Host中终止。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3069723|本文描述了不同的输出选项：PowerShell+O+is+for+Output|3069724|entityMap|0|LINK|mutability|MUTABLE|url|http://technet.microsoft.com/en-us/library/hh849921.aspx|1|http://technet.microsoft.com/en-us/library/hh849877.aspx|2|https://devcentral.f5.com/s/articles/powershell-abcs-o-is-for-output^0|1U|C|0|2C|A|1|0|D|Q|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

You can use any of these in your scenario since they write to the default streams (output and error). If you were piping output to another commandlet you would want to use <a href="http://technet.microsoft.com/en-us/library/hh849921.aspx" rel="nofollow noreferrer">Write-Output</a>, which will eventually terminate in <a href="http://technet.microsoft.com/en-us/library/hh849877.aspx" rel="nofollow noreferrer">Write-Host</a>.

This article describes the different output options: <a href="https://devcentral.f5.com/s/articles/powershell-abcs-o-is-for-output" rel="nofollow noreferrer">PowerShell O is for Output</a>

blocks|key|323306|text|我认为在这种情况下，您将需要Write-Output。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|323307|如果你有像这样的脚本|323308|Write-Output+"test1";
Write-Host+"test2";
"test3";|code-block|syntax|javascript|323309|然后，如果您调用带有重定向输出的脚本，例如yourscript.ps1+>+out.txt，您将在屏幕test1\ntest3\n中的"out.txt“中获得test2。|style|CODE|323310|请注意，"test3“和写输出行总是会在文本后追加一个新行，在PowerShell中没有办法停止这一操作(也就是说，在使用本机命令的PowerShell中，echo+-n是不可能的)。如果您想要echo+-n的功能(Bash中的一些基础和简单的功能)，请参阅samthebest's+answer。|323311|如果批处理文件运行PowerShell命令，它很可能会捕获写输出命令。我与系统管理员进行了“长时间的讨论”，讨论哪些内容应该写入控制台，哪些内容不应该写入。我们现在已经同意，如果脚本成功执行或终止，唯一的信息必须是Write-Host'ed，脚本作者可能需要知道的所有关于执行的信息(哪些项被更新，哪些字段被设置，等等)被写入输出。这样，当您向系统管理员提交脚本时，他可以轻松地runthescript.ps1+>someredirectedoutput.txt并在屏幕上看到，如果一切正常。然后将"someredirectedoutput.txt“发回给开发人员。|323312|entityMap|0|LINK|mutability|MUTABLE|url|http://technet.microsoft.com/en-us/library/hh849921.aspx|1|http://en.wikipedia.org/wiki/Bash_%2528Unix_shell%2529|2|https://stackoverflow.com/questions/2038181/how-to-output-something-in-powershell/11901810#11901810^0|E|C|0|0|0|0|L|O|1F|E|27|5|0|26|7|2P|7|30|4|1|3L|J|2|0|2Z|A|59|16|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|19|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1A|8|@$A|1B|B|1C|M|N]|$A|1D|B|1E|M|N]|$A|1F|B|1G|M|N]]|9|@]|C|$]]|$1|O|3|P|5|6|7|1H|8|@$A|1I|B|1J|M|N]|$A|1K|B|1L|M|N]]|9|@$A|1M|B|1N|1|1O]|$A|1P|B|1Q|1|1R]]|C|$]]|$1|Q|3|R|5|6|7|1S|8|@$A|1T|B|1U|M|N]|$A|1V|B|1W|M|N]]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1X|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]|12|$5|V|W|X|C|$Y|13]]]]

I think in this case you will need <a href="http://technet.microsoft.com/en-us/library/hh849921.aspx" rel="noreferrer">Write-Output</a>.

If you have a script like

<pre><code>Write-Output "test1";
Write-Host "test2";
"test3";
</code></pre>

then, if you call the script with redirected output, something like <code>yourscript.ps1 &gt; out.txt</code>, you will get <code>test2</code> on the screen <code>test1\ntest3\n</code> in the "out.txt".

Note that "test3" and the Write-Output line will always append a new line to your text and there is no way in PowerShell to stop this (that is, <code>echo -n</code> is impossible in PowerShell with the native commands). If you want (the somewhat basic and easy in <a href="http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29" rel="noreferrer">Bash</a>) functionality of <code>echo -n</code> then see <a href="https://stackoverflow.com/questions/2038181/how-to-output-something-in-powershell/11901810#11901810">samthebest's answer</a>.

If a batch file runs a PowerShell command, it will most likely capture the Write-Output command. I have had "long discussions" with system administrators about what should be written to the console and what should not. We have now agreed that the only information if the script executed successfully or died has to be <code>Write-Host</code>'ed, and everything that is the script's author might need to know about the execution (what items were updated, what fields were set, et cetera) goes to Write-Output. This way, when you submit a script to the system administrator, he can easily <code>runthescript.ps1 &gt;someredirectedoutput.txt</code> and see on the screen, if everything is OK. Then send the "someredirectedoutput.txt" back to the developers.

blocks|key|318634|text|简单地输出一些东西就是PowerShell是一件很美的事情--也是它最大的优点之一。例如，常见的Hello，World！应用程序简化为一行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|318635|"Hello,+World!"|code-block|syntax|javascript|318636|它创建一个string对象，分配前述的值，作为命令管道上的最后一项，它调用.toString()方法并将结果输出到STDOUT+(默认情况下)。一件美丽的事情。|offset|length|style|CODE|318637|其他Write-*命令特定于将文本输出到与其相关联的流，并有其各自的位置。|318638|entityMap^0|0|0|11|B|1L|6|0|2|7|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]|$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@$I|Y|J|Z|K|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

Simply outputting something is PowerShell is a thing of beauty - and one its greatest strengths. For example, the common Hello, World! application is reduced to a single line:

<pre><code>"Hello, World!"
</code></pre>

It creates a string object, assigns the aforementioned value, and being the last item on the command pipeline it calls the <code>.toString()</code> method and outputs the result to <code>STDOUT</code> (by default). A thing of beauty.

The other <code>Write-*</code> commands are specific to outputting the text to their associated streams, and have their place as such.

blocks|key|3283055|text|你根本不能让PowerShell省略那些讨厌的换行符。没有执行此操作的脚本或cmdlet。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3283056|当然，Write-Host绝对是胡说八道，因为你不能从它重定向/管道！你只需要编写你自己的代码：|3283057|using+System;

namespace+WriteToStdout
{
++++class+Program
++++{
++++++++static+void+Main(string[]+args)
++++++++{
++++++++++++if+(args+!=+null)
++++++++++++{
++++++++++++++++Console.Write(string.Join("+",+args));
++++++++++++}
++++++++}
++++}
}|code-block|syntax|javascript|3283058|例如。|3283059|PS+C:\>+writetostdout+finally+I+can+write+to+stdout+like+echo+-n
finally+I+can+write+to+stdout+like+echo+-nPS+C:\>|3283060|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You simply cannot get PowerShell to ommit those pesky newlines. There is no script or cmdlet that does this.

Of course Write-Host is absolute nonsense because you can't redirect/pipe from it! You simply have to write your own:

<pre><code>using System;

namespace WriteToStdout
{
 class Program
 {
 static void Main(string[] args)
 {
 if (args != null)
 {
 Console.Write(string.Join(" ", args));
 }
 }
 }
}
</code></pre>

E.g.

<pre><code>PS C:\&gt; writetostdout finally I can write to stdout like echo -n
finally I can write to stdout like echo -nPS C:\&gt;
</code></pre>

blocks|key|320422|text|Write-Host+"Found+file+-+"+%2B+$File.FullName+-ForegroundColor+Magenta|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|320423|品红色可以是"System.ConsoleColor“枚举值之一-黑色、DarkBlue、DarkGreen、DarkCyan、DarkRed、DarkMagenta、DarkYellow、灰色、DarkGray、蓝色、绿色、青色、红色、洋红色、黄色、白色。|unstyled|320424|%2B+$File.FullName是可选的，它显示了如何将变量放入字符串中。|offset|length|style|CODE|320425|entityMap^0|0|0|0|G|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|P|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|F|7|T|8|@]|9|@]|A|$]]]|N|$]]

<pre><code>Write-Host "Found file - " + $File.FullName -ForegroundColor Magenta
</code></pre>

Magenta can be one of the "System.ConsoleColor" enumerator values - Black, DarkBlue, DarkGreen, DarkCyan, DarkRed, DarkMagenta, DarkYellow, Gray, DarkGray, Blue, Green, Cyan, Red, Magenta, Yellow, White.

The <code>+ $File.FullName</code> is optional, and shows how to put a variable into the string.

blocks|key|3069875|text|我认为下面是Echo和Write-Host的一个很好的例子。注意test()实际上是如何返回一个int数组的，而不是一个很容易让人相信的int数组。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3069876|function+test+{
++++Write-Host+123
++++echo+456+#+AKA+'Write-Output'
++++return+789
}

$x+=+test

Write-Host+"x+of+type+'$($x.GetType().name)'+=+$x"

Write-Host+"`$x[0]+=+$($x[0])"
Write-Host+"`$x[1]+=+$($x[1])"|code-block|syntax|javascript|3069877|以上内容的终端输出：|3069878|123
x+of+type+'Object[]'+=+456+789
$x[0]+=+456
$x[1]+=+789|3069879|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/powershell/reference/5.1/microsoft.powershell.utility/Write-Host^0|B|A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

I think the following is a good exhibit of Echo vs. <a href="https://msdn.microsoft.com/powershell/reference/5.1/microsoft.powershell.utility/Write-Host" rel="noreferrer">Write-Host</a>. Notice how test() actually returns an array of ints, not a single int as one could easily be led to believe.

<pre><code>function test {
 Write-Host 123
 echo 456 # AKA 'Write-Output'
 return 789
}

$x = test

Write-Host "x of type '$($x.GetType().name)' = $x"

Write-Host "`$x[0] = $($x[0])"
Write-Host "`$x[1] = $($x[1])"
</code></pre>

Terminal output of the above:

<pre><code>123
x of type 'Object[]' = 456 789
$x[0] = 456
$x[1] = 789
</code></pre>

blocks|key|3283130|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3283131|什么是正确的东西，用来写到Windows的标准输出？|blockquote|3283132|3283133|3283134|In+effect，但very+Windows+PowerShell和PowerShell++as+v7.2，send+all+of+The6(！)++当从外部调用E222时，通过PowerShell的+将其发送到E218。|offset|length|style|BOLD|3283135|3283136|为了保留向后的compatibility.|unordered-list-item|3283137|，请参阅GitHub+issue+#7989来讨论这种可能无法修复的有问题的行为|3283138|3283139|In实践，这意味着无论您向PowerShell+发送什么PowerShell流，都将被视为外部caller:|3283140|的输出+stdout+|3283141|-+E.g.,+if+you+run+the+following+from+`cmd.exe`,+you'll+see+_no_+output,+because+the+stdout+redirection+to+`NUL`+applies+equally+to+all+PowerShell+streams:|code-block|syntax|javascript|3283142|++++-+`C:\>powershell+-noprofile+-command+"Write-Error+error!"+>NUL`|3283143|-+However+-+curiously+-+**if+you**+_**redirect+stderr**_**,+PowerShell**+_**does**_+**send+its+error+stream+to+stderr**,+so+that+with+`2>`+you+_can_+capture+the+error-stream+output+selectively;+the+following+outputs+just+`'hi'`+-+the+success-stream+output+-+while+capturing+the+error-stream+output+in+file+`err.txt`:|3283144|++++-+`C:\>powershell+-noprofile+-command+"'hi';+Write-Error+error!"+2>err.txt`|3283145|behavior+behavior为：|3283146|3283147|Send+PowerShell's+success+output++(number+_stdout**_.|3283148|+to+PowerShell|3283149|3283150|将来自all+other+streams+的输出发送到++stderr+，这是唯一的选项，因为在进程之间只存在两个输出流-用于数据的stdout+(标准输出)和用于错误消息和所有其他类型的消息的stderr(标准错误)。|3283151|3283152|3283153|It's建议在您的代码中进行这种区分，即使它当前不是respected.|3283154|3283155|3283156|Inside+PowerShell|3283157|3283158|Write-Host+is+for+display++output+，绕过成功输出流-因此，它的输出既不能(直接)在变量中捕获，也不能被抑制或取消|CODE|3283159|3283160|-+Its+original+intent+was+simply+to+create+user+feedback+and+create+simple,+console-based+user+interfaces+(colored+output).|3283161|-+Due+to+the+prior+inability+to+be+captured+or+redirected,+PowerShell+version+5+made+`Write-Host`+write+to+the+newly+introduced+_information+stream_+(number+`6`),+so+since+then+it+_is_+possible+to+capture+and+redirect+`Write-Host`+output.|3283162|3283163|Write-Error用于将non-terminating错误流错误写入错误流(编号为2)；从概念上讲，错误流相当于标准错误流。|3283164|3283165|3283166|Write-Output写入成功输出流(+1)，这在概念上等同于标准输出；它将写入+data+(results)输出流|3283167|3283168|-+However,+**explicit+use+of**+**`Write-Output`**+**is+rarely+needed**+due+to+PowerShell's+_**implicit+output**_+**feature**:+
++++-+**Output+from+any+command+or+expression+that+isn't+explicitly+captured,+suppressed+or+redirected+is**+_**automatically**_+**sent+to+the+success+stream**;+e.g.,+`Write-Output+"Honey,+I'm+$HOME"`+and+`"Honey,+I'm+$HOME"`+are+equivalent,+with+the+latter+not+only+being+more+concise,+but+also+faster.
++++-+See+[this+answer](https://stackoverflow.com/a/55665963/45375)+for+more+information.|3283169|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/PowerShell/PowerShell/issues/7989#issuecomment-430854508^0|0|0|0|0|0|2|3|C|1O|3|1S|A|24|P|2U|A|0|0|0|L|0|0|14|4|I|0|0|0|0|1I|0|0|3|4|6|0|0|0|0|0|0|8|9|A|0|0|0|X|Y|J|0|0|E|0|0|0|K|L|6|S|2A|0|0|0|0|10|0|0|0|0|6|7|A|0|0|0|H|I|7|Q|1B|0|A|0|0|0|0|0|0|13|0|B|17|1|0|0|0|0|C|E|5|16|4|1B|C|0|C|L|1|0|0|0^^$0|@$1|2|3|-4|4|5|6|2G|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|2H|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|2I|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|2J|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|2K|7|@$H|2L|I|2M|J|K]|$H|2N|I|2O|J|K]|$H|2P|I|2Q|J|K]|$H|2R|I|2S|J|K]|$H|2T|I|2U|J|K]|$H|2V|I|2W|J|K]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|2X|7|@]|8|@]|9|$]]|$1|M|3|N|4|O|6|2Y|7|@$H|2Z|I|30|J|K]]|8|@]|9|$]]|$1|P|3|Q|4|5|6|31|7|@$H|32|I|33|J|K]]|8|@$H|34|I|35|1|36]]|9|$]]|$1|R|3|-4|4|5|6|37|7|@]|8|@]|9|$]]|$1|S|3|T|4|O|6|38|7|@$H|39|I|3A|J|K]]|8|@]|9|$]]|$1|U|3|V|4|5|6|3B|7|@$H|3C|I|3D|J|K]|$H|3E|I|3F|J|K]]|8|@]|9|$]]|$1|W|3|X|4|Y|6|3G|7|@]|8|@]|9|$Z|10]]|$1|11|3|12|4|Y|6|3H|7|@]|8|@]|9|$Z|10]]|$1|13|3|14|4|Y|6|3I|7|@]|8|@]|9|$Z|10]]|$1|15|3|16|4|Y|6|3J|7|@]|8|@]|9|$Z|10]]|$1|17|3|18|4|5|6|3K|7|@$H|3L|I|3M|J|K]|$H|3N|I|3O|J|K]]|8|@]|9|$]]|$1|19|3|-4|4|5|6|3P|7|@]|8|@]|9|$]]|$1|1A|3|1B|4|O|6|3Q|7|@$H|3R|I|3S|J|K]|$H|3T|I|3U|J|K]]|8|@]|9|$]]|$1|1C|3|1D|4|5|6|3V|7|@$H|3W|I|3X|J|K]]|8|@]|9|$]]|$1|1E|3|-4|4|5|6|3Y|7|@]|8|@]|9|$]]|$1|1F|3|1G|4|O|6|3Z|7|@$H|40|I|41|J|K]|$H|42|I|43|J|K]|$H|44|I|45|J|K]]|8|@]|9|$]]|$1|1H|3|-4|4|5|6|46|7|@]|8|@]|9|$]]|$1|1I|3|-4|4|5|6|47|7|@]|8|@]|9|$]]|$1|1J|3|1K|4|O|6|48|7|@$H|49|I|4A|J|K]]|8|@]|9|$]]|$1|1L|3|-4|4|5|6|4B|7|@]|8|@]|9|$]]|$1|1M|3|-4|4|5|6|4C|7|@]|8|@]|9|$]]|$1|1N|3|1O|4|5|6|4D|7|@$H|4E|I|4F|J|K]|$H|4G|I|4H|J|K]]|8|@]|9|$]]|$1|1P|3|-4|4|5|6|4I|7|@]|8|@]|9|$]]|$1|1Q|3|1R|4|O|6|4J|7|@$H|4K|I|4L|J|K]|$H|4M|I|4N|J|K]|$H|4O|I|4P|J|K]|$H|4Q|I|4R|J|1S]]|8|@]|9|$]]|$1|1T|3|-4|4|5|6|4S|7|@]|8|@]|9|$]]|$1|1U|3|1V|4|Y|6|4T|7|@]|8|@]|9|$Z|10]]|$1|1W|3|1X|4|Y|6|4U|7|@]|8|@]|9|$Z|10]]|$1|1Y|3|-4|4|5|6|4V|7|@]|8|@]|9|$]]|$1|1Z|3|20|4|O|6|4W|7|@$H|4X|I|4Y|J|K]|$H|4Z|I|50|J|1S]|$H|51|I|52|J|1S]]|8|@]|9|$]]|$1|21|3|-4|4|5|6|53|7|@]|8|@]|9|$]]|$1|22|3|-4|4|5|6|54|7|@]|8|@]|9|$]]|$1|23|3|24|4|O|6|55|7|@$H|56|I|57|J|K]|$H|58|I|59|J|K]|$H|5A|I|5B|J|K]|$H|5C|I|5D|J|K]|$H|5E|I|5F|J|1S]|$H|5G|I|5H|J|1S]]|8|@]|9|$]]|$1|25|3|-4|4|5|6|5I|7|@]|8|@]|9|$]]|$1|26|3|27|4|Y|6|5J|7|@]|8|@]|9|$Z|10]]|$1|28|3|-4|4|5|6|5K|7|@]|8|@]|9|$]]]|29|$2A|$4|2B|2C|2D|9|$2E|2F]]]]

<blockquote>
What would be the right thing to use to write to the Windows equivalent of stdout?
</blockquote>
In effect, but very unfortunately, both Windows PowerShell and PowerShell Core as of v7.2, send all of their 6(!) <a href="https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_redirection" rel="nofollow noreferrer">output streams</a> to stdout when called from the outside, via PowerShell's <a href="https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe" rel="nofollow noreferrer">CLI</a>.
<ul>
<li>See <a href="https://github.com/PowerShell/PowerShell/issues/7989#issuecomment-430854508" rel="nofollow noreferrer">GitHub issue #7989</a> for a discussion of this problematic behavior, which likely won't get fixed, so as to preserve backward compatibility.
</li>
<li>In practice, this means that whatever PowerShell stream you send output to will be seen as stdout output by an external caller:
<ul>
<li>E.g., if you run the following from <code>cmd.exe</code>, you'll see no output, because the stdout redirection to <code>NUL</code> applies equally to all PowerShell streams:
<ul>
<li><code>C:\&gt;powershell -noprofile -command &quot;Write-Error error!&quot; &gt;NUL</code></li>
</ul>
</li>
<li>However - curiously - if you redirect stderr, PowerShell does send its error stream to stderr, so that with <code>2&gt;</code> you can capture the error-stream output selectively; the following outputs just <code>'hi'</code> - the success-stream output - while capturing the error-stream output in file <code>err.txt</code>:
<ul>
<li><code>C:\&gt;powershell -noprofile -command &quot;'hi'; Write-Error error!&quot; 2&gt;err.txt</code></li>
</ul>
</li>
</ul>
</li>
</ul>
The desirable behavior is:
<ul>
<li>Send PowerShell's success output stream (number <code>1</code>) to stdout.
</li>
<li>Send output from all other streams to stderr, which is the only option, given that between processes only 2 output streams exist - stdout (standard output) for data, and stderr (standard error) for error messages and all other types of messages - such as status information - that aren't data.
</li>
<li>It's advisable to make this distinction in your code, even though it currently isn't being respected.
</li>
</ul>
<hr />
Inside PowerShell:
<ul>
<li><code>Write-Host</code> is for display output, and bypasses the success output stream - as such, its output can neither be (directly) captured in a variable nor suppressed nor redirected.
<ul>
<li>Its original intent was simply to create user feedback and create simple, console-based user interfaces (colored output).
</li>
<li>Due to the prior inability to be captured or redirected, PowerShell version 5 made <code>Write-Host</code> write to the newly introduced information stream (number <code>6</code>), so since then it is possible to capture and redirect <code>Write-Host</code> output.
</li>
</ul>
</li>
<li><code>Write-Error</code> is meant for writing non-terminating errors to the error stream (number <code>2</code>); conceptually, the error stream is the equivalent of stderr.
</li>
<li><code>Write-Output</code> writes to the success [output] stream (number <code>1</code>), which is conceptually equivalent to stdout; it is the stream to write data (results) to.
<ul>
<li>However, explicit use of <code>Write-Output</code> is rarely needed due to PowerShell's implicit output feature:
<ul>
<li>Output from any command or expression that isn't explicitly captured, suppressed or redirected is automatically sent to the success stream; e.g., <code>Write-Output &quot;Honey, I'm $HOME&quot;</code> and <code>&quot;Honey, I'm $HOME&quot;</code> are equivalent, with the latter not only being more concise, but also faster.</li>
<li>See <a href="https://stackoverflow.com/a/55665963/45375">this answer</a> for more information.</li>
</ul>
</li>
</ul>
</li>
</ul>

I am running a PowerShell script from within a batch file. The script fetches a web page and checks whether the page's content is the string "OK".

The PowerShell script returns an error level to the batch script.

The batch script is executed by <a href="http://www.scriptftp.com" rel="noreferrer">ScriptFTP</a>, an FTP automation program. If an error occurs, I can have ScriptFTP send the full console output to the administrator via E-Mail.

In the PowerShell script, I would like to output the return value from the web site if it is not "OK", so the error message gets included in the console output, and thus in the status mail.

I am new to PowerShell and not sure which output function to use for this. I can see three:

<ul>
<li>Write-Host</li>
<li>Write-Output</li>
<li>Write-Error</li>
</ul>

What would be the right thing to use to write to the Windows equivalent of <code>stdout</code>?

How to output something in PowerShell

Windows

我正在从一个批处理文件中运行一个PowerShell脚本。该脚本获取一个网页，并检查该网页的内容是否为字符串"OK“。PowerShell脚本将错误级别返回给批处理脚本。批处理脚本由FTP自动化程序执行。如果发生错误，我可以让ScriptFTP通过电子邮件将完整的控制台输出发送给管理员。在PowerShell脚本中，如...

问如何在PowerShell中输出内容
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在PowerShell中输出内容EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在PowerShell中输出内容
EN