<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Creating custom types in PowerShell, revisited for v2</title>
	<atom:link href="http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/</link>
	<description>Jouni Heikniemi&#039;s IT adventures</description>
	<lastBuildDate>Fri, 10 Feb 2012 02:59:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Heikniemi Hardcoded &#187; PowerShell Basics #4: Matching and capturing with regular expressions</title>
		<link>http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/comment-page-1/#comment-16705</link>
		<dc:creator>Heikniemi Hardcoded &#187; PowerShell Basics #4: Matching and capturing with regular expressions</dc:creator>
		<pubDate>Sat, 13 Feb 2010 07:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/#comment-16705</guid>
		<description>[...] username and domain parts separately from the addresses. While you’re at it, you might as well construct some objects from the matches to get a cleaner view and help you manipulate the [...]</description>
		<content:encoded><![CDATA[<p>[...] username and domain parts separately from the addresses. While you’re at it, you might as well construct some objects from the matches to get a cleaner view and help you manipulate the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aleksandar</title>
		<link>http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/comment-page-1/#comment-16125</link>
		<dc:creator>Aleksandar</dc:creator>
		<pubDate>Fri, 05 Feb 2010 10:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/#comment-16125</guid>
		<description># here is a slightly different way to create a hashtable with name/value pairs

$ht = @{}
$runkey = Get-Item &#039;HKLM:\Software\Microsoft\Windows\CurrentVersion\Run&#039;

$runkey.getvaluenames() &#124; % {if ($_) {$ht.$_ = $runkey.getvalue($_)}}

new-object psobject -property $ht</description>
		<content:encoded><![CDATA[<p># here is a slightly different way to create a hashtable with name/value pairs</p>
<p>$ht = @{}<br />
$runkey = Get-Item &#039;HKLM:\Software\Microsoft\Windows\CurrentVersion\Run&#039;</p>
<p>$runkey.getvaluenames() | % {if ($_) {$ht.$_ = $runkey.getvalue($_)}}</p>
<p>new-object psobject -property $ht</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heikniemi Hardcoded &#187; PowerShell: PSObject, custom types and the add-member cmdlet</title>
		<link>http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/comment-page-1/#comment-15149</link>
		<dc:creator>Heikniemi Hardcoded &#187; PowerShell: PSObject, custom types and the add-member cmdlet</dc:creator>
		<pubDate>Wed, 20 Jan 2010 19:03:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.heikniemi.net/hardcoded/2010/01/creating-custom-types-in-powershell-revisited-for-v2/#comment-15149</guid>
		<description>[...] I’ll discuss some of the aspects involved in handling custom objects in PowerShell. Note: I have posted an update to this article regarding PowerShell v2, which cleans up the syntax described here. The theory [...]</description>
		<content:encoded><![CDATA[<p>[...] I’ll discuss some of the aspects involved in handling custom objects in PowerShell. Note: I have posted an update to this article regarding PowerShell v2, which cleans up the syntax described here. The theory [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

