Capturing Non-Standard Powershell CmdLet Output for Flow Control

Question

Currently trying to build a script utilizing cmdlets from the MS released \"Team Foundation Server Power Tools\" package.

I\'m attempting to flow command logic from the

Answer 1

Little hacky, but since I don't have TFS to try to figure something else out, see if this helps.

Answer 2

I would say that this cmdlet wasn't written correctly. First, since it didn't succeed it should have emitted an error object which would have caused $? to return false which you could have checked or trapped. Second, you can't suppress the error message using -ea 0. It looks like this snapin is using the Host api to write an error string to the host console. That's a spew!! For now, you could do what EBGreen suggests:

$msg = powershell.exe -nologo update-tfsworkspace "C:\doesnotexist\" -recurse -version T 2>&1

Just watch out for all the text your profile script spits out when a new instance of PowerShell starts up.

Answer 3

Your problem here is that the cmdlet is writing an error (Non-Terminating Error), but not throwing an exception (Terminating Error). You can make it throw an exception by adding the ErrorAction parameter:

trap{echo "fail"}
update-tfsworkspace $workspace_path -recurse -version T -ErrorAction "Stop"

This will cause the cmdlet to make all errors terminating (throwing an exception if it writes to the error stream).