Automating the world one-liner at a time…
Windows PowerShell wouldn’t be very useful without all the great cmdlets that actually manage specific technologies. We want to help cmdlet developers to create high-quality cmdlets. Today we announce availability of FxCop rules that can be used to verify compliance with some of the Cmdlet Design Guidelines as well as to find some of the common bugs.
Use the following procedure to download the required components:
Use the following procedure to configure Microsoft FxCop to run FxCop Rules for Windows PowerShell on your code:
Please refer to the FxCop Rules for Windows PowerShell project on Code Gallery for more details.
Thanks, Lukasz Anforowicz [MSFT] Windows PowerShell Developer Microsoft Corporation
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. :)
There's is a little bug in the doku for the UseCredentialAttributeForPSCredentialParameter rule. Please take a look at the "Cause" row:
"A cmdlet calls the ShouldContinue method, but it does not have a Force parameter."
That's clearly not the cause for this rule to kick in.