When I run a command with invoke-expression in Powershell, it creates a file
almost twice as large as the same thing run from command prompt. Can anyone
tell me what is going on here?

If I run the following command from a command prompt, I get a 14K text file:



dfsradmin rg list /attr:RgName,ObjState >> report.txt


If I run the following command from a Powershell prompt, I get a 27K file:

invoke-expression -command "dfsradmin rg list '/attr:RgName,ObjState' >>
report.txt"

> Can anyone tell me what is going on here?

Different encoding. Cmd.exe's redirects stdout to file using the encoding set in chcp.
PowerShell's redirection operators _always_ use Unicode encoding.

You can pipe the statement's output to Set-Content or Out-File and use UTF8 or ASCII encoding.

Get-Help about_Redirection

--
Robert

>> is an append operator, did you make sure to delete the file from the first
command before running the second? If not twice the size makes sense.

Otherwise I would explore the encoding as Uwe recommended.

"Gary" wrote:

> When I run a command with invoke-expression in Powershell, it creates a file
> almost twice as large as the same thing run from command prompt. Can anyone
> tell me what is going on here?
>
> If I run the following command from a command prompt, I get a 14K text file:
>
> dfsradmin rg list /attr:RgName,ObjState >> report.txt
>
>
> If I run the following command from a Powershell prompt, I get a 27K file:
>
> invoke-expression -command "dfsradmin rg list '/attr:RgName,ObjState' >>
> report.txt"

> Can anyone tell me what is going on here?

Different encoding. Cmd.exe's redirects stdout to file using the encoding
set in chcp.
PowerShell's redirection operators _always_ use Unicode encoding.

You can pipe the statement's output to Add-Content or Out-File and use UTF8
or ASCII encoding.

Get-Help about_Redirection

--
Robert

Thanks for the help. I am slowly trying to migrate all my command line &
batch file admin stuff to Powershell, and I never had to deal with Unicode.

"Robert Robelo" wrote:

> > Can anyone tell me what is going on here?

>
> Different encoding. Cmd.exe's redirects stdout to file using the encoding set in chcp.
> PowerShell's redirection operators _always_ use Unicode encoding.
>
> You can pipe the statement's output to Set-Content or Out-File and use UTF8 or ASCII encoding.
>
> Get-Help about_Redirection
>
> --
> Robert

It would have been nice if
Get-Help about_Redirection
had some actual examples. It does not have examples of even simple cases.
It does mention the opportunity to use Out-File cmdlet, but there are no examples.

This webpage has examples
http://ss64.com/ps/syntax-redirection.html

This article discusses the topic
http://www.johndcook.com/blog/2008/0...code-or-ascii/

- Larry


Robert Robelo wrote:

> Different encoding. Cmd.exe's redirects stdout to file using the encoding
> set in chcp.
> PowerShell's redirection operators _always_ use Unicode encoding.
>
> You can pipe the statement's output to Add-Content or Out-File and use UTF8
> or ASCII encoding.
>
> Get-Help about_Redirection
>