Invoke-WmiCommand doesn't work properly in PSv2

One of the core pieces of functionality in Invoke-WmiCommand is that it returns a proper PowerShell object. I do this in memory by using the System.Management.Automation.PSSerializer class to perform object [de]serialization. This class doesn't exist in PSv2 however. I could reimplement the logic in Import/Export-CliXml but I think I'll opt to just use Import/Export-Clixml and temporarily drop the execution results to disk and clean things up accordingly.

[secabstraction]

$obj | ConvertTo-Csv | [Convert]::ToBase64String($_)

On Tue, Dec 15, 2015 at 12:25 PM, PowerShellMafia notifications@github.com
wrote:

One of the core pieces of functionality in Invoke-WmiCommand is that it
returns a proper PowerShell object. I do this in memory by using the
System.Management.Automation.PSSerializer class to perform object
[de]serialization. This class doesn't exist in PSv2 however. I could
reimplement the logic in Import/Export-CliXml but I think I'll opt to just
use Import/Export-Clixml and temporarily drop the execution results to disk
and clean things up accordingly.

—
Reply to this email directly or view it on GitHub
#96.

That won't preserve objects though. That will just output the root properties to text in the form of a CSV.

[secabstraction]

no... just tested with this and it worked.
$obj | % { [Convert]::ToBase64String($OutputEncoding.GetBytes($)) } |
% { $OutputEncoding.GetString([Convert]::FromBase64string($)) } | ConvertFrom-Csv

Nope. No object properties here:

ps -id $PID | % { [Convert]::ToBase64String($OutputEncoding.GetBytes($_)) } | % { [Text.Encoding]::UTF8.GetString([Convert]::FromBase64string($_)) } | ConvertFrom-Csv

[secabstraction]

That's my bad, I left out the converting to csv first in that gist. my $obj was actually:

$obj = ps -Id $PID | ConvertTo-Csv

ps -Id $PID | ConvertTo-Csv | % { [Convert]::ToBase64String($OutputEncoding.GetBytes($_)) } | % { $OutputEncoding.GetString([Convert]::FromBase64string($_)) } | ConvertFrom-Csv

Sure but like I said, "That won't preserve objects though. That will just output the root properties to text in the form of a CSV." I want full object serialization - i.e. preserved embedded properties and type info. CliXml is the only way to achieve that.

$obj = ps -Id $PID | ConvertTo-Csv
$newobj = $obj | % { [Convert]::ToBase64String($OutputEncoding.GetBytes($_)) } | % { $OutputEncoding.GetString([Convert]::FromBase64string($_)) } | ConvertFrom-Csv

# This won't return the loaded modules when imported as a csv
$newobj.Modules

[secabstraction]

I should read more closely. I'll go back to my defensive meddling now.

Fixed but with reservations about having to drop a temp file to disk. Shrug...

[secabstraction]

This is ugly...

ps -id $PID | % { $thisobj = $_ ; $thisobj | gm -MemberType Property,NoteProperty,ScriptProperty | % { if ($thisobj."$($_.Name)") { $thisobj."$($_.Name)" | ConvertTo-Csv }}}