Yeah - I’m lovin’ the powerhell goodness…

But I need a way to remember all of these bits and bobs of snippets.
I guess this is what the internet is for!

This will obviously update as I find more

Basics

ExecutionPolicy

Get-ExecutionPolicy -?  

Set-ExecutionPolicy -? 

#Unrestricted 
#Default

Install Chocolatey

Just do it, ok?

chocolatey - install

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

Working with SqlServer

I think this part will end up as its own post…
Install SQL Server Powershell module

Install-Module -Name SqlServer -AllowClobber

Change password

I think this could be useful in docker instances…?

Pureinfotech - Change account password with powershell

$Password = Read-Host "Enter the new password" -AsSecureString

$UserAccount = Get-LocalUser -Name "admin"
$UserAccount | Set-LocalUser -Password $Password

Comments and more

Comments and more in powershell

This only works at the start of scripts, but is pretty cool

#Requires -RunAsAdministrator
#Requires -Version 5.0

Filesystem basics

Delete a folder

if (Test-Path -Path $Folder) {
    Remove-Item $Folder -Recurse -Force
}

List all files

Get-ChildItem -Path 'C:\SomeFolder\SomeSubFolder' -Recurse -File `
| sort fullname | SELECT fullname | Out-String -Width 256 | Out-File -FilePath 'C:\Users\User\Desktop\RAllTheFilesAndFolders.txt'

or if you want to do stuff to the strings (because you are comparing build outputs perhaps?)


$BuildThatWorksPath = "c:\WhatEva\BuildThatWorks"

if (Test-Path -Path $BuildThatWorksPath + ".txt") {
    Remove-Item $BuildThatWorksPath + ".txt"
}

Get-ChildItem -Path $BuildThatWorksPath -Recurse -File | sort fullname `
 | % {$_.fullname.replace("$BuildThatWorksPath", "-") } | Out-String -Width 256 | Out-File -FilePath $BuildThatWorksPath + ".txt"

Test Net Framework installed

This is a bit crap

https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies

Get-Childitem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'

#461814 is for Net472

Can test with mcr.microsoft.com/dotnet/framework/runtime:4.8

Persistent profile

This is for all those snippets I want to always be available, like my user secrets stuff

Adding a profile

To make a new profile for CurrentUserAllHosts
This is at %USERPROFILE%\Documents\WindowsPowerShell\profile.ps1 (but not really because my Documents folder isn’t on my home drive…)

if (!(Test-Path $Profile.CurrentUserAllHosts)) {
    New-Item -Type file -Path $Profile.CurrentUserAllHosts -Force }

Don’t forget about the executionpolicy

Profile locations

Profile Location
AllUsersAllHosts $PsHome\profile.ps1
AllUsersCurrentHost $PsHome\HostId_profile.ps1
CurrentUserAllHosts $Home\Documents\WindowsPowerShell\profile.ps1
CurrentUserCurrentHost $Home\Documents\WindowsPowerShell\HostId_profile.ps1

List all PCs on Domain

#import-module ActiveDirectory
#Get-Help Get-ADComputer -Full
cls
Get-ADComputer -Filter * -Property * | Format-Table Name,OperatingSystem,OperatingSystemServicePack,OperatingSystemVersion -Wrap –Auto #| Out-File 'Out-File.txt'

dotnet build

$versionNumber = $(Get-Date -format 'yyMM.ddhh.mmss')
dotnet build "E:\blah\MyProj.csproj" -p:Version=$versionNumber
dotnet pack "E:\blah\MyProj.csproj" -p:PackageVersion=$versionNumber --no-build

List all referenced assemblies in exe

I’ve been using this for wix setup to make sure I have the correct versions of files…
Remember that if the assembly is compiled to x86, you have to use the x86 version of the ISE/prompt

$exe = "C:\Path\To\ExeOrDll.exe"
$assembly = [System.Reflection.Assembly]::LoadFile($exe)
$dependancies = $assembly.GetReferencedAssemblies() | Sort-Object Name

Write-Output $dependancies

Credits

Pester

Secrets

Cheers!