<?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: Trap [Exception] { &#8220;In PowerShell&#8221; }</title>
	<atom:link href="http://huddledmasses.org/trap-exception-in-powershell/feed/" rel="self" type="application/rss+xml" />
	<link>http://huddledmasses.org/trap-exception-in-powershell/</link>
	<description>You can do more than breathe for free...</description>
	<pubDate>Fri, 21 Nov 2008 03:58:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cash Foley</title>
		<link>http://huddledmasses.org/trap-exception-in-powershell/comment-page-1/#comment-137470</link>
		<dc:creator>Cash Foley</dc:creator>
		<pubDate>Thu, 17 Jan 2008 11:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/trap-exception-in-powershell/#comment-137470</guid>
		<description>You qualified the Try-Finally-Catch "as long as youâ€™re able to handle all of your exceptions in a single trap".

Actually, you can nest the Try-Finally-Catch blocks effectively.  

There are a couple of side effects I've learned and I'll blog it in the near future.  In short, whenever you use a scriptblock, you effectively creates a scope for variables.  As a result, varibales created or changed in a Try Section are unavailable in the Finaly or Catch scriptblocks.  This is not a big deal but it might need to be anticipated.  Also, this is not a specific effect from Try-Finally-Catch.  It happens with all scriptblocks.  This is usually managed by "dotting" the script.  I just haven't found a way to work it into the Try-Finally-Catch commandlet.

Cash Foley</description>
		<content:encoded><![CDATA[<p>You qualified the Try-Finally-Catch &#8220;as long as youâ€™re able to handle all of your exceptions in a single trap&#8221;.</p>
<p>Actually, you can nest the Try-Finally-Catch blocks effectively.  </p>
<p>There are a couple of side effects I&#8217;ve learned and I&#8217;ll blog it in the near future.  In short, whenever you use a scriptblock, you effectively creates a scope for variables.  As a result, varibales created or changed in a Try Section are unavailable in the Finaly or Catch scriptblocks.  This is not a big deal but it might need to be anticipated.  Also, this is not a specific effect from Try-Finally-Catch.  It happens with all scriptblocks.  This is usually managed by &#8220;dotting&#8221; the script.  I just haven&#8217;t found a way to work it into the Try-Finally-Catch commandlet.</p>
<p>Cash Foley</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cash foley</title>
		<link>http://huddledmasses.org/trap-exception-in-powershell/comment-page-1/#comment-117961</link>
		<dc:creator>cash foley</dc:creator>
		<pubDate>Sun, 14 Oct 2007 05:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/trap-exception-in-powershell/#comment-117961</guid>
		<description>I made some comentary on a Try... Catch... Finally... function at 

http://cashfoley.com/2007/10/13/TryFinallyCatchInPowershell10.aspx

The origian post is by Adam Weigert  at http://weblogs.asp.net/adweigert/archive/2007/10/10/powershell-try-catch-finally-comes-to-life.aspx</description>
		<content:encoded><![CDATA[<p>I made some comentary on a Try&#8230; Catch&#8230; Finally&#8230; function at </p>
<p><a href="http://cashfoley.com/2007/10/13/TryFinallyCatchInPowershell10.aspx" rel="nofollow">http://cashfoley.com/2007/10/13/TryFinallyCatchInPowershell10.aspx</a></p>
<p>The origian post is by Adam Weigert  at <a href="http://weblogs.asp.net/adweigert/archive/2007/10/10/powershell-try-catch-finally-comes-to-life.aspx" rel="nofollow">http://weblogs.asp.net/adweigert/archive/2007/10/10/powershell-try-catch-finally-comes-to-life.aspx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
