"I use these three functions when I am working on projects that involve packaging scripts for some kind of delivery and\/or sharing scripts with and from others—mostly only when I have a folder full of files."<\/p>\n
- \n
- Parse-Script<\/b>. I borrowed this function from Windows PowerShell MVP, Keith Hill. <\/li>\n
- Find-String<\/b>. I don’t actually remember why I wrote this function. I think I wanted to use the command prompt to find files that need to change (for example, changing variable names or paths). And I think I had XML files that FINDSTR.EXE didn’t like.<\/li>\n
- Count-Lines<\/b>. This is simply a way to quantify the size of a package. It ignores empty lines and comments.<\/li>\n<\/ul>\n
Dan Bjorge<\/b> <\/span>shared two functions. The first one is a Format-History<\/b> function that accepts a history entry as input and will display the amount of time a job in the history ran. The second function is a customized Windows PowerShell prompt.<\/p>\n
Format-History function<\/b><\/p>\n
function Format-History($HistoryEntry) {<\/p>\n
if ($HistoryEntry -ne $null) {<\/p>\n
$Duration = $HistoryEntry.EndExecutionTime – $HistoryEntry.StartExecutionTime<\/p>\n
if ($Duration.Days -ge 1) {<\/p>\n
$DurationString = [String]::Format("{0:0}d{1:00}h{2:00}m{3:00}s", $Duration.Days,$Duration.Hours,$Duration.Minutes,$Duration.Seconds)<\/p>\n
} elseif($Duration.Hours -ge 1) {<\/p>\n
$DurationString = [String]::Format("{0:0}h{1:00}m{2:00}s", $Duration.Hours,$Duration.Minutes,$Duration.Seconds)<\/p>\n
} elseif($Duration.Minutes -ge 1) {<\/p>\n
$DurationString = [String]::Format("{0:0}m{1:00}.{2:000}s", $Duration.Minutes,$Duration.Seconds,$Duration.Milliseconds)<\/p>\n
} else {<\/p>\n
$DurationString = [String]::Format("{0:0}.{1:000}s", $Duration.Seconds,$Duration.Milliseconds)<\/p>\n
}<\/p>\n
<\/p>\n
return "[$DurationString] $($HistoryEntry.CommandLine)"<\/p>\n
} else {<\/p>\n
return ""<\/p>\n
}<\/p>\n
}<\/p>\n
Customized Windows PowerShell prompt<\/b><\/p>\n
function global:Prompt {<\/p>\n
$Location = (Get-Location).Path<\/p>\n
$LastCommand = Get-History -Count 1<\/p>\n
$LastCommandStr = Format-History $LastCommand<\/p>\n
<\/p>\n
$WindowTitle = "$Location | $LastCommandStr"<\/p>\n
$TabTitle = $Location<\/p>\n
if (Test-Elevated) {<\/p>\n
Write-Host "ADMIN " -NoNewline -ForegroundColor Red<\/p>\n
$WindowTitle = "[ADMIN] $WindowTitle"<\/p>\n
}<\/p>\n
<\/p>\n
Write-Host "$Location" -NoNewline<\/p>\n
<\/p>\n
if ($LastCommand -ne $null) {<\/p>\n
Write-Host " $($LastCommand.Id+1)" -NoNewline -ForegroundColor Green<\/p>\n
} else {<\/p>\n
Write-Host " 1" -NoNewline -ForegroundColor Green<\/p>\n
}<\/p>\n
<\/p>\n
if ($PsIse -ne $null) {<\/p>\n
$PsIse.CurrentPowerShellTab.DisplayName = $TabTitle<\/p>\n
} else {<\/p>\n
$Host.UI.RawUI.WindowTitle = $WindowTitle<\/p>\n
}<\/p>\n
<\/p>\n
return '> '<\/p>\n
}<\/p>\n
One cool thing that the custom prompt function does is display the admin status in red. This is shown in the following image:<\/p>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/hsg-5-20-14-1.png\" "\\"Image")
<\/a><\/p>\nDan Thompson<\/b><\/span> shared several functions that look pretty cool. One thing he does is turn on StrictM<\/b>ode<\/strong>. It is almost the first line in his Windows PowerShell profile. He then creates a Resolve-Error<\/b> function that provides useful error messages when there is a problem. He has a pushd<\/b> function that looks rather intriguing. He also has a Find-InSource<\/b> function, and a Set-WindowTitle<\/b> function.<\/p>\n
I like that Dan creates useful aliases for his functions. This makes working in the Windows PowerShell shell much easier. Here are Dan's functions:<\/p>\n
Set-StrictMode and Resolve-Error functions<\/b><\/p>\n
Set-StrictMode -Version Latest<\/p>\n
function Resolve-Error<\/p>\n
{<\/p>\n
[CmdletBinding()]<\/p>\n
param( [Parameter( Mandatory = $false, Position = 0, ValueFromPipeline = $true )]<\/p>\n
[System.Management.Automation.ErrorRecord] $ErrorRecord )<\/p>\n
<\/p>\n
process<\/p>\n
{<\/p>\n
try<\/p>\n
{<\/p>\n
if( !$ErrorRecord )<\/p>\n
{<\/p>\n
if( 0 -eq $global:Error.Count )<\/p>\n
{<\/p>\n
return<\/p>\n
}<\/p>\n
$ErrorRecord = $global:Error[ 0 ]<\/p>\n
}<\/p>\n
<\/p>\n
$global:e = $ErrorRecord<\/p>\n
$ErrorRecord | Format-List * -Force<\/p>\n
$ErrorRecord.InvocationInfo | Format-List *<\/p>\n
$Exception = $ErrorRecord.Exception<\/p>\n
for( $i = 0; $Exception; $i++, ($Exception = $Exception.InnerException) )<\/p>\n
{ "$i" * 80<\/p>\n
$Exception | Format-List * -Force<\/p>\n
}<\/p>\n
}<\/p>\n
finally { }<\/p>\n
}<\/p>\n
}<\/p>\n
Set-Alias rver Resolve-Error<\/p>\n
Pushd function<\/b><\/p>\n
function .. { pushd .. }<\/p>\n
function … { pushd ..\\.. }<\/p>\n
function …. { pushd ..\\..\\.. }<\/p>\n
function ….. { pushd ..\\..\\..\\.. }<\/p>\n
function …… { pushd ..\\..\\..\\..\\.. }<\/p>\n
function ……. { pushd ..\\..\\..\\..\\..\\.. }<\/p>\n
function …….. { pushd ..\\..\\..\\..\\..\\..\\.. }<\/p>\n
Set-Alias go Push-Location<\/p>\n
Set-Alias back Pop-Location<\/p>\n
Set-Alias l Get-ChildItem<\/p>\n
function q { exit }<\/p>\n
Find-InSource function<\/b><\/p>\n
function Find-InSource<\/p>\n
{<\/p>\n
findstr \/spinc:"$args" *.c *.cs *.cxx *.cpp *.h *.hxx *.hpp *.idl *.wxs *.wix *.wxi *.ps1 *.psm1 *.psd1<\/p>\n
}<\/p>\n
Set-Alias fs Find-InSource<\/p>\n
Set-WindowTitle function<\/p>\n
function Set-WindowTitle()<\/p>\n
{<\/p>\n
$host.ui.RawUI.WindowTitle = [String]::Join( ' ', $args )<\/p>\n
}<\/p>\n
Set-Alias 'title' 'Set-WindowTitle' -Scope Global<\/p>\n
Dave Bishop<\/b><\/span> shared the following:<\/p>\n
"I customize my prompt in (what I think) is a clever and useful way. I also load a few useful modules and tools. The big thing for me is that I created a folder on my OneDrive, and I store everything there: C:\\users\\davbish\\OneDrive\\WindowsPowerShell. I then hard link to my profile folder with junction.exe (SysInternals tool) as follows."<\/p>\n
Junction c:\\users\\davbish\\documents\\windowspowershell c:\\users\\davbish\\onedrive\\windowspowershell<\/p>\n
"I do this on all of my computers so my profile scripts (and more importantly, any edits) and certain modules follow me everywhere!"<\/p>\n
Dave also customizes his prompt function, as shown here:<\/p>\n
function Prompt<\/p>\n
{<\/p>\n
$id=1<\/p>\n
$historyItem=get-history -count 1<\/p>\n
if($historyitem)<\/p>\n
{<\/p>\n
$id=$historyItem.id+1<\/p>\n
}<\/p>\n
write-host -foregroundcolor darkgray "`n[$(get-location)]"<\/p>\n
write-host -foregroundcolor yellow -nonewline "PS:$id > "<\/p>\n
"`b"<\/p>\n
}<\/p>\n
Dave also creates an alias for Internet Explorer as follows:<\/p>\n
set-alias iexplore 'c:\\program files\\internet explorer\\iexplore.exe'<\/p>\n
Heath Stewart<\/span> <\/b>shared the following:<\/p>\n
"I added another cmdlet that I use often (although, I just finally added it to my $profile—not sure why it took me so long to do it), and you might find it useful. The idea is that sometimes you get repetitive row data like the one that follows."<\/p>\n
Key, Property, Value<\/p>\n
—, ——–, —–<\/p>\n
Foo, Name, Foo<\/p>\n
Foo, Language, 1033<\/p>\n
Foo, Id, {GUID1}<\/p>\n
Bar, Name, Bar<\/p>\n
Bar, Language, 1031<\/p>\n
Bar, Id, {GUID2}<\/p>\n
Bar, Other, Other<\/p>\n
"This happens a lot when processing metadata records that are user-definable. To create objects with the metadata properties as actual properties of a PSObject, you can use Join-Object<\/b> as follows (Property<\/b> and Value<\/b> are defaults for the second and third parameters)." This is shown here:<\/p>\n
Import-Csv foo.csv | Join-Object Key<\/p>\n
You can download the function from GitHub: Join-Object cmdlet<\/a>.<\/p>\n
Jason Chenault<\/b><\/span> provided the following:<\/p>\n
"I found this function useful when I was supporting Exchange Server 2010. I used it whenever I needed a quick report about disconnected mailboxes or simply to clean the databases."<\/p>\n
function Get-DisconnectedMailbox {<\/p>\n
<\/p>\n
param(<\/p>\n
<\/p>\n
[String]$Name = '*',<\/p>\n
[String]$Server = '*',<\/p>\n
[Switch]$Clean,<\/p>\n
[Switch]$Archive<\/p>\n
<\/p>\n
)<\/p>\n
<\/p>\n
if ($Clean) {<\/p>\n
Get-MailboxDatabase | Clean-MailboxDatabase<\/p>\n
}<\/p>\n
<\/p>\n
$databases = Get-MailboxDatabase | ?{$_.Name -like $Server}<\/p>\n
$databases | %{<\/p>\n
$db = Get-Mailboxstatistics -database $_.Name |<\/p>\n
?{$_.DisconnectDate -and $_.IsArchiveMailbox -eq $Archive}<\/p>\n
<\/p>\n
$db | ?{$_.displayname -like $Name} |<\/p>\n
Select-Object DisplayName,<\/p>\n
MailboxGuid,<\/p>\n
Database,<\/p>\n
DisconnectReason,<\/p>\n
ItemCount,<\/p>\n
disconnectDate | Out-file -append DiscMBReport.txt<\/p>\n
}<\/p>\n
}<\/p>\n
Thank-you all for sharing portions of your profiles. I think it is cool to see what people add into their Windows PowerShell profile. It is interesting that several of the people I highlighted today customized their Windows PowerShell prompt, and several wrote search\/find functions. I like Dave Bishop's idea about storing stuff on OneDrive so it follows him around. I really love the Join-Object<\/b> function from Heath. <\/p>\n
Join me tomorrow when we will look into more profiles. It will be way cool, just wait and see. So let me ask you, “What’s in your profile?” Post a comment and let us know.<\/p>\n
I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n
Ed Wilson, Microsoft Scripting Guy<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":"
Summary: Microsoft Scripting Guy, Ed Wilson, talks to various Windows PowerShell users about what is in their profiles. Microsoft Scripting Guy, Ed Wilson, is here. I have had this idea floating in my head, and I decided to reach out to some fellow Windows PowerShell experts and enthusiasts in regards to “What is in your […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[144,3,4,45],"class_list":["post-1315","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-profiles","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"
Summary: Microsoft Scripting Guy, Ed Wilson, talks to various Windows PowerShell users about what is in their profiles. Microsoft Scripting Guy, Ed Wilson, is here. I have had this idea floating in my head, and I decided to reach out to some fellow Windows PowerShell experts and enthusiasts in regards to “What is in your […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/1315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=1315"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/1315\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=1315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=1315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=1315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Find-String<\/b>. I don’t actually remember why I wrote this function. I think I wanted to use the command prompt to find files that need to change (for example, changing variable names or paths). And I think I had XML files that FINDSTR.EXE didn’t like.<\/li>\n