<?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"
	>
<channel>
	<title>Comments on: Release: PowerShell Community Extensions 1.1</title>
	<atom:link href="http://pshell.info/basics/162/release-powershell-community-extensions-11/feed/" rel="self" type="application/rss+xml" />
	<link>http://pshell.info/basics/162/release-powershell-community-extensions-11/</link>
	<description>PowerShell for Everyone</description>
	<pubDate>Wed, 08 Sep 2010 23:32:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Heath Stewart</title>
		<link>http://pshell.info/basics/162/release-powershell-community-extensions-11/#comment-52</link>
		<dc:creator>Heath Stewart</dc:creator>
		<pubDate>Fri, 16 Mar 2007 15:05:42 +0000</pubDate>
		<guid isPermaLink="false">http://pshell.info/basics/162/release-powershell-community-extensions-11/#comment-52</guid>
		<description>Instead of expecting FileInfo[], you could in sub-script use convert-path to convert the provider-qualified PSPath from many objects (including my own get-msiproductinfo and get-msipatchinfo you blogged about :) to a provider-specific path. Too bad convert-path didn't allow you to limit resolution to a specific, user-defined set of providers.</description>
		<content:encoded><![CDATA[<p>Instead of expecting FileInfo[], you could in sub-script use convert-path to convert the provider-qualified PSPath from many objects (including my own get-msiproductinfo and get-msipatchinfo you blogged about <img src='http://pshell.info/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> to a provider-specific path. Too bad convert-path didn&#8217;t allow you to limit resolution to a specific, user-defined set of providers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
