ChrisLGardner

#requires -Module Reflection
function Find-Dependencies {
    param($Path)

    Get-ParseResults $Path | 
        Find-Token { $_ -is "System.Management.Automation.Language.CommandAst" } | 
        Get-Command -Name { $_.CommandElements[0].Value } -ea continue | # Errors will appear for commands you don't have available
        Sort Source, Name | 
        Group Source |
        Select @{N="Module";e={$_.Name}}, @{N="Used Commands";E={$_.Group}}

ChrisLGardner

Credit: Mark Krauss
Website: https://get-powershellblog.blogspot.com

Collection Type Guidence

When to use what

• Use Arrays if you know the element types and have a fixed length and/or known-up-front collection size that will not change.
• Use ArrayList if you have an unkown collection size with either unknown or mixed type elements.
• Use a Generic List when know the type of the elements but not the size of the collection.
• Use a HashTable if you are going to do key based lookups on a collection and don't know the object type of the elements.
• Use a Dictionary<TKey, TValue> you are going to do key based lookups on a collection and you know the type of the elements.
• Use a HashSet when you know the type of elements and just want unique values and quick lookups and assignmnets.

ChrisLGardner

<#
    .SYNOPSIS
        Wrap commands with DebuggerNonUserCode attribute to prevent the PowerShell debugger stepping into them
    .DESCRIPTION
        Generates proxy functions that wrap the original commands, and put an attribute on the proxy to prevent the debugger stopping.
    .EXAMPLE
        Get-Command -Module Pester | Hide-FromDebugger

        Hides all pester functions from the debugger, so you can debug in your code without stepping into Pester functions.
#>