Kapil Borle

@daviwil Sorry for getting back so late about this. Sure, you can assign this to me if you haven't started work on it already.

Yes, I think we will have it merged by then.

@mattpwhite you didn't miss anything. Unfortunately, the way to write an external .net assembly rule is not documented and even if you were to write such a rule, it is...

I think I would use such a rule and would be a good addition to the current set.

I think we can target this for v1.2 iteration.

cc @joeyaiello Right now, Invoke-ScriptAnalyzer by itself doesn't have such a capability. However, a workaround would be to filter out the *.tests.ps1 files and pipe the remaining files to Invoke-ScriptAnalyzer....

I think this happens because scritpanalyzer [finds](https://github.com/PowerShell/PSScriptAnalyzer/blob/db61dd64b015d6f858161f743224c703d79d7a70/Engine/ScriptAnalyzer.cs#L1162) two scriptblocks and run the rule on those two scriptblocks: ```powershell PS> {Describe "a" { >> "b" | Should Throw >> }}.Ast.FindAll({$args[0] -is...

If you are writing a rule in `C#` you need to walk the Ast. But, if you write it in `PowerShell` then ScriptAnalyzer gives you all the instances of the...

By the definition of `ScriptBlockAst` [here](https://msdn.microsoft.com/en-us/library/system.management.automation.language.scriptblockast(v=vs.85).aspx), it is supposed to be the root node. So, sending all the nested ScriptBlocksAsts to the custom rule probably doesn't make much sense. I...