http://blogs.msdn.com/b/powershell/archive/2010/03/30/testing-cmdlets-with-fxcop.aspxWindows PowerShell wouldn’t be very useful without all the great cmdlets that actually manage specific technologies.&#160; We want to help cmdlet developers to create high-quality cmdlets.&#160; Today we announce availability of FxCop rules that can been-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/powershell/archive/2010/03/30/testing-cmdlets-with-fxcop.aspx#9991604Wed, 07 Apr 2010 08:05:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:9991604Joey<p>There's is a little bug in the doku for the UseCredentialAttributeForPSCredentialParameter rule. Please take a look at the &quot;Cause&quot; row:</p> <p>&quot;A cmdlet calls the ShouldContinue method, but it does not have a Force parameter.&quot;</p> <p>That's clearly not the cause for this rule to kick in.</p> <p>thanks</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9991604" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2010/03/30/testing-cmdlets-with-fxcop.aspx#9987859Wed, 31 Mar 2010 02:20:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:9987859Joshua Einstein<p>Great idea! This will certainly help cmdlet authors fall into the pit of success. Almost makes me want to re-write all my advanced functions (which were previously snapins) in C# again. :)</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9987859" width="1" height="1">