PowerShell 3 PSCustomObject displays in stupid mode via a variable

Question

PowerShell 3.0 gave us PSCustomObject as a type which allows proper table formatting, like this:

> [PSCustomObject]@{ Day = "Monday"; Task = "Wash car" }

Day     Task
---     ----
Monday   Wash car

(see http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2012/04/13/Custom-objects-default-display-in-PowerShell-3-0.aspx)

But if I go via a variable, it reverts to stupid mode.

> [PSCustomObject]$row = @{ Day = "Monday"; Task = "Wash car" }
> $row

Name    Value
---     ----
Task    Wash car
Day     Monday

Why? (thanks)

Luke Puplett · Accepted Answer · 2013-02-19 21:40:57Z

1

Solved it almost immediately.

[PSCustomObject]$row = [PSCustomObject]@{ Day = "Monday"; Task = "Wash car" }

Effectively, I was creating and casting a hashtable to a PSCustomObject. Still not entirely sure why the hashtable keys aren't turned into properties like a .NET 4.0 DLR ExpandoObject.

Much better to write CmdLets in C#.

answered Feb 19, 2013 at 21:40

Luke Puplett

45.9k55 gold badges205 silver badges291 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Benjamin Hubbard Over a year ago

Just want to note that in PowerShell 2, this would still result in type Hashtable, not PSCustomObject. Had this same exact issue and couldn't figure it out till I saw this question and realized that my issue is the PowerShell version.

Collectives™ on Stack Overflow

PowerShell 3 PSCustomObject displays in stupid mode via a variable

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related