JustinGrote

throw 'This has moved to https://github.com/JustinGrote/ModuleFast'

indented-automation

using namespace System.Collections.Generic; using namespace System.Text

Add-Type -TypeDefinition '
    using System;
    using System.Runtime.InteropServices;
    using System.Text;

    public class WindowTools
    {
        public delegate bool EnumWindowsProc(IntPtr hWnd, int lParam);

IISResetMe

class BigIntRange : System.Collections.IEnumerable
{
    [bigint]$from
    [bigint]$to

    [bool]$Descending

    BigIntRange([bigint]$from,[bigint]$to)
    {
        $this.from = $from

JustinGrote

using namespace System.Net.Http
#requires -version 7.2
# This is the bootstrap script for Modules
[CmdletBinding(PositionalBinding = $false)]
param (
	#Specify a specific release to use, otherwise 'latest' is used
	[string]$Release = 'latest',
	#Specify the user
	[string]$User = 'JustinGrote',
	#Specify the repo

indented-automation

function Split-DistinguishedName {
    <#
    .SYNOPSIS
        Split a distinguishedName into named pieces.

    .DESCRIPTION
        Split a distinguishedName into Name, ParentDN, ParentName, and DomainComponent.

    .EXAMPLE
        Split-DistinguishedName 'OU=somewhere,DC=domain,DC=com'

jborean93

# Copyright: (c) 2020, Jordan Borean (@jborean93) <[email protected]>
# MIT License (see LICENSE or https://opensource.org/licenses/MIT)

Function Get-SmbShareInfo {
    <#
    .SYNOPSIS
    Enumerate shares on a remote host.
    
    .DESCRIPTION
    Enumerate shares on a remote host and returns the name, type, and special remark for those shares.

Jaykul

This is always my answer to all those "compile your .ps1" solutions that are floating around. Why would you wrap your PowerShell in an exe and some custom host?

Just paste this header on the top of your PowerShell script, and then before you share it, rename it with the .cmd extension. While you're writing, it's a nice syntax-highlighted PowerShell script, and when you rename it, *poof* it's double-clickable. Drop it in the PATH and you can execute it from the Run dialog or from PowerShell, batch, whatever.

Because there are still people around who actually use CMD, I've updated it to show how to handle passing parameters.

A couple of notes:

1. It runs with ExecutionPolicy unrestricted because if you're still using CMD you probably haven't configured your ExecutionPolicy
2. It uses -NoProfile to make sure the environment is the same on everyone's PC...
3. It only creates function :: {} because that allows us to ignore the :: on the first line

Jaykul

function New-Hyperlink {
    <#
        .SYNOPSIS
            Creates a VT Hyperlink in a supported terminal such as Windows Terminal 1.4+
        .NOTES
            There's a more powerful version of this, with color support and more, in PANSIES
        .EXAMPLE
            New-Hyperlink https://github.com/Jaykul/PANSIES PANSIES

            Creates a hyperlink with the text PANSIES which links to the github project

SeeminglyScience

using namespace System.Management.Automation

# Use of StopUpstreamCommandsException is obviously not supported. Subject to breaking at any time.

function Select-FirstObject {
    [Alias('first', 'top')]
    [CmdletBinding(PositionalBinding = $false)]
    param(
        [Parameter(ValueFromPipeline)]
        [psobject] $InputObject,

Jaykul

function Measure-CommandEx {
    <#
        .SYNOPSIS
            A from-scratch approach to timing command execution using Stopwatch
    #>
    [CmdletBinding()]
    param(
        # The command to test (accepts value from pipeline)
        [Parameter(ValueFromPipeline)]
        [ScriptBlock[]]$Command,