kevinblumenfeld

Credit: Mark Kraus
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.

mklement0

<#

  Prerequisites: PowerShell v5.1 and above (verified; may also work in earlier versions)
  License: MIT
  Author:  Michael Klement <mklement0@gmail.com>

  DOWNLOAD and DEFINITION OF THE FUNCTION:

    irm https://gist.github.com/mklement0/9e1f13978620b09ab2d15da5535d1b27/raw/Time-Command.ps1 | iex

timothywarner

How to Become a Microsoft MVP (https://timw.info/mvp)

Tim Warner' Contact info

• MVP profile
• Twitter
• LinkedIn
• Pluralsight
• Website

andypiper

Built using Shields.io

Served from https://twbadges.glitch.me

jdhitsolutions

#requires -version 4.0

Function New-GitHubGist {

[cmdletbinding(SupportsShouldProcess,DefaultParameterSetName = "Content")]
Param(
[Parameter(Position = 0, Mandatory, HelpMessage = "What is the name for your gist?",ValueFromPipelineByPropertyName)]
[ValidateNotNullorEmpty()]
[string]$Name,

stevenkuhn

#
# Assumptions
#
# 1. If you have a Octopus release deployed, say 1.0.0.73, there is a git
#    tag set for that commit in GitHub that is "v1.0.0.73".
#
# 2. You have TeamCity label each successful build in GitHub with the format
#    "v{build number}. Sidenote: it appears that TeamCity only labels the
#    default branch, but not feature branches.
#

Jaykul

The simplest way to enforce rules on PowerShell class properties is to set the Type of the property, of course. But sometimes you want something a little bit more clever than that. One solution is to use a Validate* attribute, like ValidateRange or ValidateLength or ValidateSet attribute...

However, you can write your own, by just deriving from ValidateArguments() or something that derives from that, like the ValidateEnumeratedArguments class allows you to validate a whole array of items.

For instance, a simple validator would be one that validates uniqueness, based on a specific property. Our validator will be created fresh each time it's used, and then each item in the array will be passed through ValidateElement, so this works:

using namespace System.Collections.Generic
usin

jdhitsolutions

#requires -version 7.0

$am = @"
  _____           __  __  ___              _                 __    ______
 / ___/__ ___ ___/ / /  |/  /__  _______  (_)__ ___ _    __ / /__ / _/ _/
/ (_ / _ \ _ \ _  / / /|_/ / _ \/ __/ _ \/ / _ \ _ `/   / // / -_) _/ _/
\___/\___\___\_,_/ /_/  /_/\___/_/ /_//_/_/_//_\_, ( )  \___/\__/_//_/
                                              /___/|/
"@

potatoqualitee

# mute here: https://twitter.com/settings/muted_keywords
republicans
democrats
sanders
manafort
comey
koch
kkk
ku klux klan
TERF

Jaykul

# Add a .ToDictionary(KeyType,ValueType) for all hashtables
Update-TypeData -TypeName Hashtable -MemberType ScriptMethod -MemberName ToDictionary -Value {
param([Type]$KeyType,[Type]$ValueType)
    [Scriptblock]::Create(
        "[Enumerable]::ToDictionary(
            [DictionaryEntry[]]@(`$this.GetEnumerator()),
            [Func[DictionaryEntry,$($KeyType.FullName)]]{ `$args.Key },
            [Func[DictionaryEntry,$($ValueType.FullName)]]{ `$args.Value })"
    ).Invoke()
}