PowerShell is a great tool. But it is not perfect. This is not a problem if one knows the pitfalls and ways to avoid them. PowerShellTraps is a collection of some traps and oddities shown by demo scripts and covered by automated tests. One of the goals is to test future PowerShell versions and see what changes.
For simplicity some demo scripts require that the current PowerShell location is set to their directory. But this is not needed for automated tests, they take care of proper current locations themselves. See also TESTS.
Contributions are welcome, see CONTRIBUTING.
- Basic
- And-and-or-have-same-precedence
- Break-and-Continue-with-not-matching-label
- Break-and-Continue-without-loop
- Cannot-pipe-some-expressions
- Compound-equality-operators
- Count-and-Length-in-Strict-Mode
- Count-and-Length-of-mixed-objects
- Dynamic-switch-parameter
- Enums-are-always-evaluated-to-true
- Errors-of-unusual-type
- Extra-properties-of-IDictionary
- Function-invoked-like-method
- Invocation-with-odd-paths
- Logical-operators-with-collections
- Null-converted-to-empty-string
- Number-of-returned-objects
- Requires
- Switch-is-a-looping-construct
- Tempting-wrong-operators
- Too-simple-function-names
- Trap-creates-a-new-scope
- Trap-with-continue
- Trap-with-no-break-or-continue
- Try-and-trap-catch-terminating-errors
- Unexpected-output
- Unrolled-collections
- ValidateScript-attribute
- Clixml
- Cmdlets
- Module
- PowerShell.exe