This blog article is the third in a series of learning about the PowerShell Abstract Syntax Tree (AST). Be sure to read the other two if you haven't already.
Learning about the PowerShell Abstract Syntax Tree (AST)
Learn about the PowerShell Abstract Syntax Tree (AST) – Part 2
Learn about the PowerShell Abstract Syntax Tree (AST) – Part 3
In this blog article, I'll be specifically focusing on finding the AST recursively.
I'll start off by storing the path to one of my functions Read more [...]
In my previous blog article a few weeks ago on "Learning about the PowerShell Abstract Syntax Tree (AST)", I mentioned there was an easier way to retrieve the AST so that you didn't have to cast everything to a script block. There are two .NET static methods, ParseFile and ParseInput, that are part of the Parser class in the System.Management.Automation.Language namespace which can be used to retrieve the AST.
First, I’ll store the content of one of my functions in a variable.
The Read more [...]
1 | $Code = Get-Content -Path U:\GitHub\Hyper-V\MrHyperV\public\Get-MrVmHost.ps1 -Raw |
I recently received a request to write a script for monitoring IIS websites and their application pools on a specific Windows 2012 R2 server and start them if they were stopped. This is something I created fairly quickly and thought I would share.
I always try to centralize any scripts I write and have them run on a job server instead of the actual server they're querying. That way I don't have multiple versions of the same script floating around on different servers. I can easily use this same Read more [...]
Last month I decided to embark on a networking project to rid my home of poor connectivity. I tweeted out asking about the benefits of Cat 6 cable since I already owned enough Cat 5e to complete the entire project.
The primary benefit of Cat 6 cable for a home environment seems to be future proofing since Cat 5e is perfectly capable of Gigabit. Ultimately, the free Cat 5e cable won out because it left more money in the budget for new networking equipment. If I had to pay someone to install Read more [...]
My computer recently updated to Windows 10 version 1809 and as with all previous major updates of Windows 10, this wipes out the Remote Server Administration Tools (RSAT).
However, unlike previous versions, Microsoft has now made RSAT available via Features on Demand and while you're supposed to be able to install them from the GUI, they never showed up as being an option for me.
That's not really a problem though since they can now be installed via PowerShell. Who needs a GUI anyway?
The Read more [...]
This week, I'll continue where I left off in my previous blog article "PowerShell Script Module Design Philosophy".
Moving forward, the development versions of my PowerShell script modules will use a non-monolithic design where each function is dot-sourced from the PSM1 file. When I move them to production, I'll convert them to using a monolithic design where all functions reside in the PSM1 file. In development, each PS1 file uses a Requires statement which specifies the requirements from a PowerShell Read more [...]
Years ago, when I first learned how to create PowerShell script modules, I built them with all the functions in one huge monolithic PSM1 file. I like the monolithic script module design from a performance and security standpoint along with the ease of signing fewer files if you’re taking advantage of code signing to digitally sign your scripts and modules (there are fewer files to sign). What I don’t like is that collaborating with others using one huge file is a merge conflict waiting for a Read more [...]
Using asterisks (*) in your module manifest is a bad idea no matter how you look at it. First, your module will be slower because it will have to figure out what to export. More importantly, if you use a "#Requires -Modules" statement in your functions and they're in separate PS1 files, all of the specified module's commands will show as being part of your module.
I'll pick up where I left off in one of my previous blog articles "PowerShell Script Module Design: Plaster Template for Creating Modules". Read more [...]
My preferred indentation style when writing PowerShell code is Stroustrup style because I don't like my code to cuddle (there's no cuddled else in Stroustrup style). I occasionally hear from others that they don't like this style because it doesn't work from the PowerShell console.
While it doesn't work by default, there's a trick to making that style work from the PowerShell console. Simply press Shift+Enter instead of just Enter at the end of the line before Read more [...]
1 2 3 4 5 6 | if ($plasterParams.Git) { $ModulePath = "$($plasterParams.DestinationPath)\$($plasterParams.GitRepoName)\$($plasterParams.Name)" } else { $ModulePath = "$($plasterParams.DestinationPath)\$($plasterParams.Name)" } |
I recently began updating my PowerShell script module build process. Updating my Plaster template was one of the first things I needed to do. If you haven't already read my blog article about "Using Plaster to create a PowerShell Script Module template", I'd recommend beginning there as this blog article assumes you already have a basic understanding of how to use Plaster.
All of the information from my previous Plaster template is still there with the exception of the required PowerShell version Read more [...]
First, I'd recommend reading my blog article "Announcing the PowerShell Conference Book" if you haven't.
In early May of this year (2018), I came up with the idea of what would become "The PowerShell Conference Book". On the evening of May 6th, I sent an email to Don Jones and Jeff Hicks asking what they thought and if they'd be interested in writing a chapter in the book. The next morning, I'd received positive responses from both of them, confirming that they would be interested in participating.
Leanpub Read more [...]
There's been a lot of debate about script module design as of lately and instead of tweeting something out asking for responses, I thought I would post it here via a blog article.
Back when I first started creating PowerShell script modules, I placed all of my functions in the PSM1 file and later started placing each function in a separate PS1 file that was dot-sourced from the PSM1 file.
I would simply place the PS1 files in the root folder of the script module. Read more [...]
1 2 3 4 5 | #Dot source all functions in all ps1 files located in the module folder Get-ChildItem -Path $PSScriptRoot\*.ps1 -Exclude *.tests.ps1, *profile.ps1 | ForEach-Object { . $_.FullName } |
A couple of days ago, one of my kids asked me "What day of the week will it be in 11 days from now?". My response was "I'm not sure, but I can tell you how to figure out the answer for yourself". Open up PowerShell, wrap Get-Date in parentheses, place a dot or period afterwards, followed by AddDays, then 11 in another set of parentheses, and finally another dot or period followed by DayOfWeek.
Want to know what the day of the week was 11 days ago instead? Read more [...]
1 | (Get-Date).AddDays(11).DayOfWeek |
PowerShell Saturday Chattanooga was this past weekend. I attended the all-day preconference presented by Jeff Hicks on Friday which saw a great turn out of about 50 people or so.
I presented two 45-minute sessions as part of the Saturday event. One on "Writing award winning PowerShell functions and script modules" and another on "Recreate MOF based DSC resources as Class based DSC resources". The code and slide decks from both of my presentations can be found in my presentations repo on GitHub. Read more [...]
I was recently named as one of the top 21 SysAdmin influencers, bloggers, and geeks to follow on this years' SysAdmin Day by IT Chronicles.
I'm humbled and honored to be part of their list. There are also several other Microsoft Cloud and Datacenter Management MVP's for Windows PowerShell on the list. If your interested in PowerShell (and you probably are if you're reading this blog site), I'd recommend taking a look at the original article on the IT Chronicles website.
µ Read more [...]
One of the companies that I support is currently in the process of migrating from an on-premises Exchange Server environment to Office 365. They're currently running in hybrid mode. While it seems like wanting to know what mailboxes still exist onsite versus which ones are in the cloud would be an all too common task, there doesn't seem to be an easy way to get that information with PowerShell. You would think that you'd be able to run a PowerShell command and it would return the results. Well, not Read more [...]