Why is Powershell ISE showing errors that Powershell console does not show?

Question

I\'m running exactly the same script.ps1 file in a Powershell ISE (manually loading the script and pressing F5) and in a Powershell console (executing the script file).

Answer 1

I don't know why they output differently, but the message that we see from git push is coming over stderr. This means that they are both showing errors, although the ISE is making them much louder, and converting it into error objects.

Consider this output from the PowerShell prompt:

PS> git push
Everything up-to-date
PS> git push 2> $null    # Redirect stderr to $null
PS> $LastExitCode
1
PS>

and compare it to the ISE:

PS> git push
git : Everything up-to-date
At line:1 char:1
+ git push
+ ~~~~~~~~
    + CategoryInfo          : NotSpecified: (Everything up-to-date:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
PS> git push 2> $null
PS> $LastExitCode
1
PS>

Except for the extra output from the error object being displayed, the output is the same. The ISE has converted the stderr string to a NativeCommandError object, and it does even display the error message if you look past the red.

Answer 2

as shown in this Stackoverflow answer to prevent git push to print to STDERR the solution is to call the command witn --porcelain option.

then, calling

git push origin master --porcelain

output goes all to STDOUT

Answer 3

So, the example below case have any error , this command -q 2>&1 | %{ "$_" }` will nullifying the result of errors.

A solution and use: git push -q 2>&1 | %{ "$_" }

Answer 4

Hmmm, the only major difference I can think of right off the top of my head is that the ISE uses single-threaded apartment (STA) mode in v2, and the console uses multi-threaded apartment (MTA). Have you tried running powershell.exe with the -STA argument, or powershell_ise.exe with -MTA, and trying the script again?

It looks like the error is coming from the Git command you're trying to run, FWIW.