blocks|key|907102|text|要写入文件，可以使用字节数组。下面的示例创建一个空的ZIP文件，您可以向其中添加文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907103|[Byte[]]+$zipHeader+=+80,+75,+5,+6,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0,+0
[System.IO.File]::WriteAllBytes("C:\My.zip",+$zipHeader)|code-block|syntax|javascript|907104|或使用：|907105|[Byte[]]+$text+=+[System.Text.Encoding]::UTF8.getBytes("Enabling+feature+XYZ.......")
[System.IO.File]::WriteAllBytes("C:\My.zip",+$text)|907106|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

To write to a file you can use a byte array. The following example creates an empty ZIP file, which you can add files to:

<pre><code>[Byte[]] $zipHeader = 80, 75, 5, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
[System.IO.File]::WriteAllBytes("C:\My.zip", $zipHeader)
</code></pre>

Or use:

<pre><code>[Byte[]] $text = [System.Text.Encoding]::UTF8.getBytes("Enabling feature XYZ.......")
[System.IO.File]::WriteAllBytes("C:\My.zip", $text)
</code></pre>

blocks|key|907156|text|虽然它在您的情况下可能不起作用(因为您向用户提供了信息性输出)，但您可以创建一个可用于附加输出的字符串。当需要输出时，只需输出字符串即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907157|当然，忽略这个例子在你的例子中是愚蠢的，但在概念上是有用的：|907158|$output+=+"Enabling+feature+XYZ......."
Enable-SPFeature...
$output+%2B=+"Done"
Write-Output+$output|code-block|syntax|javascript|907159|显示：|907160|Enabling+feature+XYZ.......Done|907161|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|$]]

While it may not work in your case (since you're providing informative output to the user), create a string that you can use to append output. When it's time to output it, just output the string.

Ignoring of course that this example is silly in your case but useful in concept:

<pre><code>$output = "Enabling feature XYZ......."
Enable-SPFeature...
$output += "Done"
Write-Output $output
</code></pre>

Displays: 

<pre><code>Enabling feature XYZ.......Done
</code></pre>

blocks|key|1122119|text|对FrinkTheBrave的回答进行简化：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122120|[System.IO.File]::WriteAllText("c:\temp\myFile.txt",+$myContent)|code-block|syntax|javascript|1122121|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

A simplification to FrinkTheBrave's response:

<pre><code>[System.IO.File]::WriteAllText("c:\temp\myFile.txt", $myContent)
</code></pre>

blocks|key|907261|text|我遇到的问题是，在使用PowerShell+v2时，写输出实际上会对输出进行换行，至少对标准输出是这样。我试图将一个XML文本写入stdout，但没有成功，因为它在字符80处很难包装。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907262|解决方法是使用|907263|[Console]::Out.Write($myVeryLongXMLTextBlobLine)|code-block|syntax|javascript|907264|这在PowerShell+v3中不是问题。那里的Write-Output似乎工作正常。|907265|根据PowerShell脚本的调用方式，您可能需要使用|907266|[Console]::BufferWidth+=<+length+of+string,+e.g.+10000)|907267|在您写入stdout之前。|907268|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

The problem that I hit was that Write-Output actually linebreaks the output when using using PowerShell v2, at least to stdout. I was trying to write an XML text to stdout without success, because it would be hard wrapped at character 80.

The workaround was to use

<pre><code>[Console]::Out.Write($myVeryLongXMLTextBlobLine)
</code></pre>

This was not an issue in PowerShell v3. Write-Output seems to be working properly there.

Depending on how the PowerShell script is invoked, you may need to use

<pre><code>[Console]::BufferWidth =&lt; length of string, e.g. 10000)
</code></pre>

before you write to stdout.

blocks|key|907377|text|shufler的答案是正确的。另一种说法是:不是使用数组形式将值传递到写入输出，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907378|Write-Output+"Parameters+are:"+$Year+$Month+$Day|code-block|syntax|javascript|907379|或通过多次调用写入输出来实现等效项，|907380|Write-Output+"Parameters+are:"
Write-Output+$Year
Write-Output+$Month
Write-Output+$Day
Write-Output+"Done."|907381|首先将组件连接到一个字符串变量中：|907382|$msg="Parameters+are:+$Year+$Month+$Day"
Write-Output+$msg|907383|这将防止由于多次调用Write-Output+(或数组形式)而导致的中间CRLF，但当然不会抑制Write-Output命令小程序的最终CRLF。为此，您必须编写自己的命令小程序，使用此处列出的其他复杂的变通方法之一，或者等到微软决定支持写输出的-NoNewline选项。|offset|length|style|CODE|907384|您希望向控制台提供文本进度指示器(即"....")与写入日志文件相反，还应通过使用Write-Host来满足。您可以通过将msg文本收集到一个变量中以写入日志，并使用Write-Host向控制台提供进度来完成这两项任务。可以将此功能组合到您自己的命令小程序中，以实现最大程度的代码重用。|907385|entityMap^0|0|0|0|0|0|0|3F|A|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|14|8|@$Q|15|R|16|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

The answer by shufler is correct. Stated another way: Instead of passing the values to Write-Output using the ARRAY FORM,

<pre><code>Write-Output "Parameters are:" $Year $Month $Day
</code></pre>

or the equivalent by multiple calls to Write-Output,

<pre><code>Write-Output "Parameters are:"
Write-Output $Year
Write-Output $Month
Write-Output $Day
Write-Output "Done."
</code></pre>

concatenate your components into a STRING VARIABLE first:

<pre><code>$msg="Parameters are: $Year $Month $Day"
Write-Output $msg
</code></pre>

This will prevent the intermediate CRLFs caused by calling Write-Output multiple times (or ARRAY FORM), but of course will not suppress the final CRLF of the Write-Output commandlet. For that, you will have to write your own commandlet, use one of the other convoluted workarounds listed here, or wait until Microsoft decides to support the <code>-NoNewline</code> option for Write-Output.

Your desire to provide a textual progress meter to the console (i.e. "....") as opposed to writing to a log file, should also be satisfied by using Write-Host. You can accomplish both by collecting the msg text into a variable for writing to the log AND using Write-Host to provide progress to the console. This functionality can be combined into your own commandlet for greatest code reuse.

blocks|key|907438|text|不幸的是，正如在一些回答和评论中指出的那样，Write-Host可能是危险的，并且不能通过管道传输到其他进程，并且Write-Output没有-NoNewline标志。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|907439|但这些方法是显示进度的"*nix“方式，"+PowerShell”方式似乎是Write-Progress：它在PowerShell窗口的顶部显示进度信息栏，从PowerShell+3.0开始提供，see+manual提供详细信息。|907440|#+Total+time+to+sleep
$start_sleep+=+120

#+Time+to+sleep+between+each+notification
$sleep_iteration+=+30

Write-Output+(+"Sleeping+{0}+seconds+...+"+-f+($start_sleep)+)
for+($i=1+;+$i+-le+([int]$start_sleep/$sleep_iteration)+;+$i%2B%2B)+{
++++Start-Sleep+-Seconds+$sleep_iteration
++++Write-Progress+-CurrentOperation+("Sleep+{0}s"+-f+($start_sleep))+(+"+{0}s+..."+-f+($i*$sleep_iteration)+)
}
Write-Progress+-CurrentOperation+("Sleep+{0}s"+-f+($start_sleep))+-Completed+"Done+waiting+for+X+to+finish"|code-block|syntax|javascript|907441|以OP的例子为例：|907442|#+For+the+file+log
Write-Output+"Enabling+feature+XYZ"

#+For+the+operator
Write-Progress+-CurrentOperation+"EnablingFeatureXYZ"+(+"Enabling+feature+XYZ+...+"+)

Enable-SPFeature...

#+For+the+operator
Write-Progress+-CurrentOperation+"EnablingFeatureXYZ"+(+"Enabling+feature+XYZ+...+Done"+)

#+For+the+log+file
Write-Output+"Feature+XYZ+enabled"|907443|entityMap|0|LINK|mutability|MUTABLE|url|https://technet.microsoft.com/en-us/library/hh849902.aspx^0|M|A|1L|C|1Z|A|0|12|E|2Q|A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|H|3|I|5|J|7|1B|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1C|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|1D|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

Unfortunately, as noted in several answers and comments, <code>Write-Host</code> can be dangerous and cannot be piped to other processes and <code>Write-Output</code> does not have the <code>-NoNewline</code> flag.

But those methods are the "*nix" ways to display progression, the "PowerShell" way to do that seems to be <code>Write-Progress</code>: it displays a bar at the top of the PowerShell window with progress information, available from PowerShell 3.0 onward, <a href="https://technet.microsoft.com/en-us/library/hh849902.aspx" rel="noreferrer" title="Write-Progress on MS TechNet">see manual</a> for details.

<pre><code># Total time to sleep
$start_sleep = 120

# Time to sleep between each notification
$sleep_iteration = 30

Write-Output ( "Sleeping {0} seconds ... " -f ($start_sleep) )
for ($i=1 ; $i -le ([int]$start_sleep/$sleep_iteration) ; $i++) {
 Start-Sleep -Seconds $sleep_iteration
 Write-Progress -CurrentOperation ("Sleep {0}s" -f ($start_sleep)) ( " {0}s ..." -f ($i*$sleep_iteration) )
}
Write-Progress -CurrentOperation ("Sleep {0}s" -f ($start_sleep)) -Completed "Done waiting for X to finish"
</code></pre>

And to take the OP's example:

<pre><code># For the file log
Write-Output "Enabling feature XYZ"

# For the operator
Write-Progress -CurrentOperation "EnablingFeatureXYZ" ( "Enabling feature XYZ ... " )

Enable-SPFeature...

# For the operator
Write-Progress -CurrentOperation "EnablingFeatureXYZ" ( "Enabling feature XYZ ... Done" )

# For the log file
Write-Output "Feature XYZ enabled"
</code></pre>

blocks|key|907472|text|它可能不是非常优雅，但它完全符合OP的要求。请注意，ISE会处理StdOut，因此不会有输出。为了查看此脚本的工作情况，它不能在ISE中运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907473|$stdout=[System.Console]::OpenStandardOutput()
$strOutput="Enabling+feature+XYZ...+"
$stdout.Write(([System.Text.Encoding]::ASCII.GetBytes($strOutput)),0,$strOutput.Length)
Enable-SPFeature...
$strOutput="Done"
$stdout.Write(([System.Text.Encoding]::ASCII.GetBytes($strOutput)),0,$strOutput.Length)
$stdout.Close()|code-block|syntax|javascript|907474|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

It may not be terribly elegant, but it does exactly what OP requested. Note that the ISE messes with StdOut, so there will be no output. In order to see this script work it can't be run within the ISE.

<pre><code>$stdout=[System.Console]::OpenStandardOutput()
$strOutput="Enabling feature XYZ... "
$stdout.Write(([System.Text.Encoding]::ASCII.GetBytes($strOutput)),0,$strOutput.Length)
Enable-SPFeature...
$strOutput="Done"
$stdout.Write(([System.Text.Encoding]::ASCII.GetBytes($strOutput)),0,$strOutput.Length)
$stdout.Close()
</code></pre>

blocks|key|907540|text|是的，因为其他答案都有状态，所以不能使用Write-Output来完成。在PowerShell失败的地方，求助于.NET，这里甚至有几个.NET答案，但它们比需要的更复杂。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|907541|只需使用：|907542|[Console]::Write("Enabling+feature+XYZ.......")
Enable-SPFeature...
Write-Output+"Done"|code-block|syntax|javascript|907543|它不是最纯粹的PowerShell，但它可以工作。|907544|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Yes, as other answers have states, it cannot be done with Write-Output. Where PowerShell fails, turn to .NET, there are even a couple of .NET answers here but they are more complex than they need to be.

Just use:

<pre><code>[Console]::Write("Enabling feature XYZ.......")
Enable-SPFeature...
Write-Output "Done"
</code></pre>

It is not purest PowerShell, but it works.

blocks|key|1122519|text|Write-Host很可怕，是世界的破坏者，但您可以在使用Write-Output进行日志记录时，仅使用它向用户显示进度(不是OP要求日志记录)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1122520|Write-Output+"Enabling+feature+XYZ"+%7C+Out-File+"log.txt"+#+Pipe+to+log+file
Write-Host+-NoNewLine+"Enabling+feature+XYZ......."
$result+=+Enable-SPFeature
$result+%7C+Out-File+"log.txt"
#+You+could+try{}catch{}+an+exception+on+Enable-SPFeature+depending+on+what+it's+doing
if+($result+-ne+$null)+{
++++Write-Host+"complete"
}+else+{
++++Write-Host+"failed"
}|code-block|syntax|javascript|1122521|entityMap^0|0|A|T|C|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

<code>Write-Host</code> is terrible, a destroyer of worlds, yet you can use it just to display progress to a user whilst using <code>Write-Output</code> to log (not that the OP asked for logging).

<pre class="lang-bsh prettyprint-override"><code>Write-Output "Enabling feature XYZ" | Out-File "log.txt" # Pipe to log file
Write-Host -NoNewLine "Enabling feature XYZ......."
$result = Enable-SPFeature
$result | Out-File "log.txt"
# You could try{}catch{} an exception on Enable-SPFeature depending on what it's doing
if ($result -ne $null) {
 Write-Host "complete"
} else {
 Write-Host "failed"
}
</code></pre>

blocks|key|1122625|text|我作弊了，但我相信这是解决所有需求的唯一答案。也就是说，这避免了尾随CRLF，同时为其他操作提供了完成的位置，并在必要时正确地重定向到stdout。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122626|$c_sharp_source+=+@"
using+System;
namespace+StackOverflow
{
+++public+class+ConsoleOut
+++{
++++++public+static+void+Main(string[]+args)
++++++{
+++++++++Console.Write(args[0]);
++++++}
+++}
}
"@
$compiler_parameters+=+New-Object+System.CodeDom.Compiler.CompilerParameters
$compiler_parameters.GenerateExecutable+=+$true
$compiler_parameters.OutputAssembly+=+"consoleout.exe"
Add-Type+-TypeDefinition+$c_sharp_source+-Language+CSharp+-CompilerParameters+$compiler_parameters

.\consoleout.exe+"Enabling+feature+XYZ......."
Write-Output+'Done.'|code-block|syntax|javascript|1122627|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I cheated, but I believe this is the only answer that addresses every requirement. Namely, this avoids the trailing CRLF, provides a place for the other operation to complete in the meantime, and properly redirects to stdout as necessary.

<pre><code>$c_sharp_source = @"
using System;
namespace StackOverflow
{
 public class ConsoleOut
 {
 public static void Main(string[] args)
 {
 Console.Write(args[0]);
 }
 }
}
"@
$compiler_parameters = New-Object System.CodeDom.Compiler.CompilerParameters
$compiler_parameters.GenerateExecutable = $true
$compiler_parameters.OutputAssembly = "consoleout.exe"
Add-Type -TypeDefinition $c_sharp_source -Language CSharp -CompilerParameters $compiler_parameters

.\consoleout.exe "Enabling feature XYZ......."
Write-Output 'Done.'
</code></pre>

blocks|key|907704|text|$host.UI.Write('Enabling+feature+XYZ.......')
Enable-SPFeature...
$host.UI.WriteLine('Done')|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|907705|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>$host.UI.Write('Enabling feature XYZ.......')
Enable-SPFeature...
$host.UI.WriteLine('Done')
</code></pre>

blocks|key|1122693|text|desired+o/p:启用功能XYZ......Done|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122694|您可以使用下面的命令|1122695|$a+=“启用功能XYZ”|1122696|写输出"$a......Done“|1122697|您必须在引号中添加变量和语句。希望这能对您有所帮助:)|1122698|感谢Techiegal|1122699|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

desired o/p:
Enabling feature XYZ......Done

you can use below command

$a = "Enabling feature XYZ"

Write-output "$a......Done"

you have to add variable and statement inside quotes. hope this is helpful :)

Thanks 
Techiegal

blocks|key|1122740|text|最简单的方式是行内连接--同时转移到“Write-Output”；例如，2个制表符(字符串)&然后是字面/逐字(字符串)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122741|Write-Output+("`t`t"+%2B+'${devArg}')|code-block|syntax|javascript|1122742|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Simplest way with in-line concatenation - and while moving across to 'Write-Output' instead; e.g. 2 tab characters (string) &amp; then a literal/verbatim (string):
<pre><code>Write-Output (&quot;`t`t&quot; + '${devArg}')
</code></pre>

blocks|key|1122814|text|我无论如何都不是专家，但为什么不这样：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122815|Write-Output+"hello"+%7C+ForEach-Object+{++$PSItem.Trim()+}+%7C+Do-Whatever|code-block|syntax|javascript|1122816|这保持了流水线的语义，但在将其向下传递到流水线之前，只修剪了换行符，无论下一步需要做什么。如果这是在写文件，那就写吧。如果是写入主机，则可以执行此操作，但如果确实要写入主机，请记住使用%7C+Write-Host+-NoNewline|offset|length|style|CODE|1122817|更新:根据我下面的评论：“我明白为什么我的答案不起作用了……当通过管道连接到外部程序时，Powershell不可避免地会附加一个新的行字符作为其管道语义的一部分。请看这个:+github.com/PowerShell/PowerShell/issues/5974因此，当我在管道中传递经过修剪的文本时，新的行字符将重新出现在输入中。”|1122818|entityMap^0|0|0|2K|N|0|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]]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I'm not an expert by any means, but why not this:
<pre><code>
Write-Output &quot;hello&quot; | ForEach-Object { $PSItem.Trim() } | Do-Whatever
</code></pre>
This maintains the pipeline semantics but just trims the new line characters before passing it on down the pipeline to whatever you need to do next. If that is writing to a file, so be it. If that is writing to the host, you can do that, but if you do write it to the host, remember to use <code>| Write-Host -NoNewline</code>
UPDATE: As per my comment below: &quot;I see why my answer won't work.. Powershell inevitable appends a new line char as part of it's piping semantics when piping to external programs. See this: github.com/PowerShell/PowerShell/issues/5974 Therefore when I pass the trimmed text down the pipeline, the new line char will re-appear in the input.&quot;

I want my PowerShell script to print something like this:

<pre><code>Enabling feature XYZ......Done
</code></pre>

The script looks something like this:

<pre><code>Write-Output "Enabling feature XYZ......."
Enable-SPFeature...
Write-Output "Done"
</code></pre>

But <code>Write-Output</code> always prints a new-line at the end so my output isn't on one line. Is there a way to do this?

How do I output text without a newline in PowerShell?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我希望我的PowerShell脚本打印如下内容：Enabling feature XYZ......Done该脚本如下所示：Write-Output "Enabling feature XYZ......."Enable-SPFeature...Write-Output "Done"但是Write-Output总是在末...

问如何在PowerShell中输出没有换行符的文本？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在PowerShell中输出没有换行符的文本？EN