Note<\/b> This is Part 5 of a nine-part series about building your own Windows PowerShell cmdlet. Read the entire series<\/a> as it unfolds.<\/p>\n Here’s Sean…<\/p>\n Yesterday, we introduced some common parameters that are now available to our cmdlet:<\/p>\n -Verbose<\/p>\n<\/li>\n -Debug<\/p>\n<\/li>\n -WarningAction<\/p>\n<\/li>\n -WarningVariable<\/p>\n<\/li>\n -ErrorAction<\/p>\n<\/li>\n -ErrorVariable<\/p>\n<\/li>\n -OutVariable<\/p>\n<\/li>\n -OutBuffer<\/p>\n<\/li>\n<\/ul>\n Now we can modify our existing advanced function to leverage some of these parameters.<\/p>\n We are already using the Write-Error<\/b> cmdlet. We can also add Write-Debug<\/b> in various points of the script to show the values of our variables for troubleshooting.<\/p>\n function global:ADD-LOGFILE{<\/p>\n <\/p>\n [CmdletBinding(<\/p>\n DefaultParameterSetName=”Folder”,<\/p>\n SupportsShouldProcess=$True,<\/p>\n ConfirmImpact=’High’<\/p>\n )]<\/p>\n <\/p>\n PARAM(<\/p>\n [STRING[]]$Folder=”C:\\PowerShell”,<\/p>\n [STRING[]]$Preface=”Logfile”,<\/p>\n [STRING[]]$Extension=”.log”<\/p>\n )<\/p>\n <\/p>\n WRITE-DEBUG “`$Folder: $Folder”<\/p>\n WRITE-DEBUG “`$Preface: $Preface”<\/p>\n WRITE-DEBUG “`$Extension: $Extension”<\/p>\n <\/p>\n # GET the Current Date for our Logfile<\/p>\n <\/p>\n $Today=GET-DATE<\/p>\n WRITE-DEBUG “`$Today: $Today”<\/p>\n # Extract the Date removing the “\/”<\/p>\n <\/p>\n $Date=$Today.toshortdatestring().Replace(“\/”,””)<\/p>\n WRITE-DEBUG “`$Date: $Date”<\/p>\n <\/p>\n # Extract the Time removing the “:”<\/p>\n <\/p>\n $Time=$Today.tostring(“HH:mm:ss”).Replace(“:”,”“)<\/p>\n WRITE-DEBUG “`$Time: $Time”<\/p>\n <\/p>\n # Build our Filename<\/p>\n <\/p>\n $Logfilename=$Folder+”\\”+$Preface+”-“+$Date+”-“+$Time+$Extension<\/p>\n WRITE-DEBUG “`$Logfilename: $Logfilename”<\/p>\n <\/p>\n # Test and ensure file does not already exist<\/p>\n <\/p>\n IF (TEST-PATH -path $Logfilename)<\/p>\n <\/p>\n { WRITE-ERROR –message “Error: $Logfilename exists.” –category ‘WriteError’<\/p>\n <\/p>\n # If file exists, return a status of Boolean $False for Unsuccessful<\/p>\n <\/p>\n RETURN $Logfilename,$FALSE }<\/p>\n <\/p>\n ELSE<\/p>\n <\/p>\n {<\/p>\n <\/p>\n # Create logfile<\/p>\n <\/p>\n NEW-ITEM –Type File -path $Logfilename -Force | OUT-NULL<\/p>\n WRITE-DEBUG “$Logfilename successfully created”<\/p>\n <\/p>\n # Return the Full path and filename if successful<\/p>\n <\/p>\n RETURN $Logfilename,$TRUE<\/p>\n <\/p>\n }<\/p>\n }<\/p>\n We’ll save this as a new Windows PowerShell script called addlogcmdlet.ps1 and execute it to create the new cmdlet in memory.<\/p>\n With these new changes to our cmdlet, we can troubleshoot and view the variables within the cmdlet (or whatever output we choose reveal) by adding the Verbose<\/b> parameter.<\/p>\n We can even have our cmdlet pause and ask us what to do if an error occurs by leveraging the ErrorAction <\/b>parameter.<\/p>\n ~Sean<\/p>\n Thank you, Sean. The cmdlet is really coming together. Nice additions today. Guest Blogger Week will continue tomorrow when Sean will talk more about building a cmdlet.<\/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 <\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Microsoft Windows PowerShell MVP, Sean Kearney, continues a series of guest blogs detailing building your own cmdlet. Microsoft Scripting Guy, Ed Wilson, is here. Guest blogger and Windows PowerShell MVP, Sean Kearney, has written a series about building cmdlets. For more about Sean, see his previous guest blog posts. Note This is Part 5 […]<\/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":[372,56,3,154,45],"class_list":["post-4876","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-build-your-own-cmdlet","tag-guest-blogger","tag-scripting-guy","tag-sean-kearney","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Microsoft Windows PowerShell MVP, Sean Kearney, continues a series of guest blogs detailing building your own cmdlet. Microsoft Scripting Guy, Ed Wilson, is here. Guest blogger and Windows PowerShell MVP, Sean Kearney, has written a series about building cmdlets. For more about Sean, see his previous guest blog posts. Note This is Part 5 […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4876","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=4876"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4876\/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=4876"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=4876"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=4876"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/2234.hsg-10-3-12-1.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/0488.hsg-10-3-12-2.png\" "\\"Image")
<\/a><\/p>\n