<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Top five gotchas when learning PowerShell</title>
	<link>http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/</link>
	<description>The blog of John D. Cook</description>
	<pubDate>Thu, 21 Aug 2008 18:13:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Keith Hill</title>
		<link>http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/#comment-343</link>
		<dc:creator>Keith Hill</dc:creator>
		<pubDate>Mon, 05 May 2008 23:49:26 +0000</pubDate>
		<guid>http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/#comment-343</guid>
		<description>I agree with all except #2.  I've never had nor heard of many issues with ` as an escape character and thank goodness they didn't use \ as an escape character (like in Korn shell).  One gotcha that I would consider perhaps in the top five is calling out to external apps that take parameters.  Sometimes PowerShell's parsing gets in the way like if your parameters use semi-colon e.g. /workspace:hillr1;hillr.  PoSh sees the semi-colon as a statement separator and considers hillr the start of a new command.  Ugh, this has caused me and a lot of folks grief (which is why we added echoargs.exe to PSCX).  Another popular gotcha is using expressions within double quotes.  I see folks doing this "Host version is $host.version" not realizing that it should be "Host version is $($host.version)".  Just my 2 cents.  BTW good stuff you're writing on Posh.  Keep it up!</description>
		<content:encoded><![CDATA[<p>I agree with all except #2.  I&#8217;ve never had nor heard of many issues with ` as an escape character and thank goodness they didn&#8217;t use \ as an escape character (like in Korn shell).  One gotcha that I would consider perhaps in the top five is calling out to external apps that take parameters.  Sometimes PowerShell&#8217;s parsing gets in the way like if your parameters use semi-colon e.g. /workspace:hillr1;hillr.  PoSh sees the semi-colon as a statement separator and considers hillr the start of a new command.  Ugh, this has caused me and a lot of folks grief (which is why we added echoargs.exe to PSCX).  Another popular gotcha is using expressions within double quotes.  I see folks doing this &#8220;Host version is $host.version&#8221; not realizing that it should be &#8220;Host version is $($host.version)&#8221;.  Just my 2 cents.  BTW good stuff you&#8217;re writing on Posh.  Keep it up!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
