http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/ The blog of John D. Cook Sat, 11 Feb 2012 22:42:11 -0500 http://wordpress.org/?v=2.8.4 hourly 1 http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/comment-page-1/#comment-46234 Tweets that mention Top five gotchas when learning PowerShell — The Endeavour -- Topsy.com Sun, 12 Sep 2010 17:15:40 +0000 http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/#comment-46234 [...] This post was mentioned on Twitter by Scott Muc, Andy Parkhill. Andy Parkhill said: Top five gotchas when learning PowerShell #bookmark #powershell http://icio.us/wyeoye [...] [...] This post was mentioned on Twitter by Scott Muc, Andy Parkhill. Andy Parkhill said: Top five gotchas when learning PowerShell #bookmark #powershell http://icio.us/wyeoye [...]

]]> http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/comment-page-1/#comment-343 Keith Hill Mon, 05 May 2008 23:49:26 +0000 http://www.johndcook.com/blog/2008/05/02/top-five-gotchas-when-learning-powershell/#comment-343 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! 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!

]]>