<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Dude, where’s my script ?</title><link>http://blogs.technet.com/b/jamesone/archive/2008/10/17/dude-where-s-my-script.aspx</link><description>I’ve been working on a PowerShell script over the last few days which uses an XML file. (That’s another post in the stack). I had a nagging question about how to figure out where the script file is in order to because that’s where the XML file needs to</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Dude, where’s my script ?</title><link>http://blogs.technet.com/b/jamesone/archive/2008/10/17/dude-where-s-my-script.aspx#3139555</link><pubDate>Tue, 21 Oct 2008 06:50:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3139555</guid><dc:creator>Lee Holmes</dc:creator><description>&lt;p&gt;Yes, as mentioned in the recipe -- putting the code in a function is the crucial point to prevent an ugly conditional statement. An alternative is &amp;quot;&amp;amp; { $myInvocation.ScriptName }&amp;quot;, but that looks too idiomatic for my liking.&lt;/p&gt;
&lt;p&gt;Lee&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3139555" width="1" height="1"&gt;</description></item></channel></rss>