So it’s a new year, so naturally that means a new static site generator! Instead of writing a blog post like I planned, I’ve ripped out my old static site generator (Statiq) and replaced it with Hugo. But, at least for the month of January I plan to post at least 3 times! So I’ve got that going for me 😄

So I’ve have this domain for just about two years now. What have I done with it? Exactly nothing! So… I’ve been eyeing up Statiq for a while. Finally I’ve moved my old site over to this one, with all of the blog posts. What’s going to be on here? No idea! Mostly just my ramblings. Perhaps some rants about what’s bothering at the moment. For now, have some old posts that are probably no longer relevant, but they’re still here just in case.

The other day I needed to fix something on my children’s laptops. This brought to my attention that when I set them up I had given them admin. Naturally this is not an ideal setup. But the issue becomes: How do I grant them the ability to install software without needing to reach out to me too often. Quite simply, they need the ability to run installations as an administrator, but not the ability to just become administrator.

What is the best part of the PowerShell community? That’s an excellent question. As a community, we have numerous places to gather and exchange ideas, obtain advice, share our expertise, form relationships that extend beyond the confines of an office building. The Why 🔗One of those places is Discord and Slack as well as on Freenode in the #powershell channel. The Discord and Slack are bridged together by a bot. This bot also loops in Freenode in a channel known as #bridge.

Late in 2018, I had the distinct pleasure of spending a few hours with @FredWeinmann. We spent the time fixing up my PSCUCM Module (Available from the PowerShell Gallery and GitHub). During this session we went through a number of commands and setups utilizing his PSModuleDevelopment module and PSFramework. What will ensue is a multi-part series on Developing PowerShell Modules using PSFramework and PSModuleDevelopment. And so, without further ado, I present part 1:

This is a foray into getting started with the vscode-powershell extension. In particular noting some of the perhaps less obvious things I needed to do in order to get it to build on Ubuntu 18.04. First thing you’ll need to do of course is to fork the repository. There are two repositories that we want to fork to our github account: PowerShellEditorService and vscode-powershell. Once you’ve forked them (and perhaps made hours of work that Tiler and Rob keep harrassing you as not being good enough…) you need to clone them to your local machine.