<?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>Arguments what are they good for</title><link>http://blogs.technet.com/b/christwe/archive/2011/11/16/arguments-what-are-they-good-for.aspx</link><description>If your like me you have slowly (or maybe quickly) been getting frustrated with using arguments in your PowerShell scripts, they have none of the nice built in functionality that function parameters have like Named, Mandatory, etc . 
 On the Pro side</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Arguments what are they good for</title><link>http://blogs.technet.com/b/christwe/archive/2011/11/16/arguments-what-are-they-good-for.aspx#3465821</link><pubDate>Thu, 17 Nov 2011 11:15:32 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3465821</guid><dc:creator>PSNewbie</dc:creator><description>&lt;p&gt;As an alternate solution, we use configuration files to parametrize our scripts using xml files. You don&amp;#39;t have to worry about parameter order, xml is easy to use with powershell.&lt;/p&gt;
&lt;p&gt;Using Read-Host to get the parameters makes easier to ensure the script gets all the parameters, but as newcomers to powershell is important to us to triple check the values we are entering.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3465821" width="1" height="1"&gt;</description></item></channel></rss>