During the recent PowerShell+DevOps Global Summit I had two primary presentations, that is, traditional sessions with slides and demos. My other sessions were panels which means if you weren’t in the room you missed out on some great content and interaction.
Anyway….my main sessions were on creating class-based PowerShell tools and using Nano server in the datacenter. The former was a lightening fast 45 minute session where I tried to cram in as much as I could. The latter was a 90 minute walkthrough of building a variety of Nano server images to meet traditional datacenter roles. Again, there’s no substitute for attending.
But for those of you who couldn’t attend, all of my demo files are available on GitHub.
I realize not everyone has jumped on to GitHub yet. You don’t need a GitHub account to get these files. No need to fork or clone. All you have to do is click on the green “clone or download” button and download a zip file. Of course you are welcome to clone the repo if you’d like.
As far as recordings go, this was not a good year. My Nano server session was not recorded and I don’t know yet about the class-based tools session.
Thanks to everyone who attended my sessions. I hope you found them worth your time.
I’ve recently returned from Bellevue, WA and the 5th annual PowerShell+DevOps Summit. Each year our event has grown and this year I think we’ve crossed over into being the PowerShell-related event you should attend. I spoke with many attendees who couldn’t stress enough how much they were getting out of the conference. For some, the conference paid for itself within the first 30 minutes. A significant barometer for me is the number of attendees who either paid for the conference out of their own pocket or burned vacation days to attend. Hopefully their employers will recognize the value and offer some assistance next year. And even though we had some nasty hiccups between flights, family emergencies and flaky recording equipment, I can’t think of a single person I met that wasn’t coming back next year.
One of the primary benefits of attending this event, is the opportunity to hear directly from the PowerShell product team at Microsoft, including Technical Fellow Jeffrey Snover.
This is your chance to communicate directly with key members of the team to voice your concerns, praise or questions. You also get a rare glimpse into what the team is working on and where we’re going with all of this.
But more than anything, I have started to recognize attendees of this event as a tribe. Complete with respected elders.
We are a passionate group bound together with a very strong common set if interests and goals. We may be split into different clans such as Chef-adherents, DSC fans and Linux devotees, but we all want each other to succeed and we have each other’s backs.
And of course the community “feasting” is legendary.
I hope that next year you’ll consider joining the tribe. There isn’t much of an initiation ceremony other than getting involved and no tattoo is required!
Next year’s event runs April 9-12. Astute observers will recognize this as the same dates this year, but we are moving to a Monday-Thursday format. We plan on a slight increase in the number of available seats but you should expect that next year will also be a sell-out event. You should keep an eye on https://powershell.org/summit/ as well as the #PSHSummit tag on Twitter.
If you attended this year, I’d love to hear your thoughts on the event and its value to you.
Today’s Friday Fun post, as most of these are, is a little silly and a little educational. Because I obviously am avoiding getting any real work accomplished, I worked on a little project that would add a border around a string of text. I often write formatted text to the screen to display information and thought it would be nice to be able to add sometime of border.
A few days ago I posted an entry that explained how to create and use snippets in Visual Studio Code. As mentioned in that article I’m attempting to make the transition to VSCode for all my PowerShell work. Being able to use snippets is just one feature that I rely on. And as a number of people pointed out, there are VSCode extensions that will make this easy to do. Install the Easy Snippet Maker extension and you’ll get a context menu to turn any selected text into a snippet.
Follow the prompts and if creating a PowerShell snippet it will be added to the PowerShell.json file I showed previously. But there’s more you can do with snippets, even after you’ve created them. This is fun.
So I’ve recently moved my daily work to a different laptop, a Yoga 900 with 16GB of RAM to be exact. I had been running Windows 8.1 but decided to jump in completely to a Windows 10 environment. As part of the process I’ve also made it a goal to begin using Visual Studio Code (VS Code) for my PowerShell work. Like many of you I am heavily invested in the PowerShell ISE so I know this won’t be easy. I’ve customized the PowerShell ISE extensively and have a lot of muscle memory that will need to be re-trained. One of the most important elements for me are snippets.