Comments on: Essential PowerShell: Name your custom object types

By: How do I create a custom type in PowerShell for my scripts to use? - Programmers Goodies

Tue, 05 Jul 2011 09:57:13 +0000

[...] Naming Custom Objects [...]

By: Tweak actions’ type associations « Dmitry’s PowerBlog: PowerShell and beyond

Tue, 09 Jun 2009 10:02:43 +0000

[...] You can associate an action with a tree node (rather than the object type) by manually adding your own special type to the objects your node emits: e.g. $myObject.PSObject.TypeNames.Insert(0,'MyObjectTypeName') – see this post for more information on manipulating PowerShell types. [...]

By: Mike Shepard

Mike Shepard — Sun, 21 Dec 2008 00:53:10 +0000

Great tip! I have a lot of functions that return lists of datarows. By adding a typename that is more descriptive, I can create formats and type definitions for them in ps1xml files. Makes things look a lot nicer.

By: karl prosser

karl prosser — Thu, 10 Jul 2008 04:26:21 +0000

great to see somebody else caring about this and using this technique. I thought i was the only one.

By: Episode 32 – Citrix does PowerShell « PowerScripting Podcast

Episode 32 – Citrix does PowerShell « PowerScripting Podcast — Mon, 07 Jul 2008 12:26:34 +0000

[...] From Poshoholic: Essential PowerShell: Name your custom object types [...]

By: Essential PowerShell: Define default properties for custom objects « Poshoholic

Sat, 05 Jul 2008 07:25:15 +0000

[...] PowerShell: Define default properties for custom objects After posting my blog entry about naming your custom object types on Thursday, Hal Rottenberg left me a comment saying how it’s a shame that you have to [...]

By: Kirk Munro

Kirk Munro — Fri, 04 Jul 2008 02:42:19 +0000

You know what, I started typing in a reply saying that someone should create one or more scripts, functions, cmdlets, etc. to handle this sort of thing, and then it dawned on me that in many cases, if not the majority, you don’t even really need it. I mean, realistically, when you create a custom object all you really care about are the default properties to display in your output, right? You’re already adding your own members on the fly, so you don’t really need a types.ps1xml file, and any other formatting you would want to apply can be done using expressions in the Format-Table or Format-List cmdlet. Thanks for making me think twice about this and check out this follow-up post: http://poshoholic.com/2008/07/05/essential-powershell-define-default-properties-for-custom-objects/!

By: Hal Rottenberg

Hal Rottenberg — Thu, 03 Jul 2008 22:34:35 +0000

This is a really cool technique, Kirk, thanks. The only thing I regret is that type formatting must be done via external files. I suppose you could generate a ps1xml inline and call it but that ought not be necessary.