Our September 2015 puzzle is another one-liner, to help get you out of Summer Mood and back into Work Mode. This time, it’s a pretty real-world scenario, designed to test your understanding of the pipeline and how data can be manipulated within it. You’ll need to really grasp pipeline parameter binding to make this work in the shortest command possible.
Our August 2015 puzzler tests your ability to retrieve data from the Web. If you’ve never done this before, it can be a real brain-bender - but don’t overthink it; experts can probably pull this off in a one-liner if they’re using a newer version of PowerShell!
The July puzzler wasn’t intended to break your brain - but it was intended to highlight an extremely important pipeline technique - and to make you think about how PowerShell parses command lines. Let’s begin with our Celebrity Entry, from Boe Prox. We think you’ll discover some interesting new techniques in this answer - and learn from understanding how he got there. Celebrity Entry The 2015 Scripting Games have started and have taken a different route this year in that we are they are running a monthly puzzle vs.
Our July 2015 puzzler is designed to make you really think about the PowerShell parser. Normally, you can more or less ignore the parser, because if you’re typing best-practice, long-form code (no aliases, spell out parameter names, etc), the parser deals really well with everything. But knowing how the parser works is useful, because when you get into tricky syntax, the parser can be harder to work with. So we’re going to test the limits of the parser’s patience - and your skills!
I know a lot of folks have been wondering about when the next Scripting Games will be. It’s a complicated answer… so bear with me for a minute while I unburden my soul to you. If you prefer to just skip the explanations, you can skip a bit to see what we’re doing, part 1. The Background I’m not sure how long Microsoft’s Scripting Guys ran The Scripting Games, but it goes back at least to 2006.
We have some folks working on the next Scripting Games… but we want some feedback from the community to make sure we’re offering something of value. The current plan is to run a series of events, with both Beginner and Intermediate tracks. There will be no “advanced” track; the feeling is that, if you’re advanced, you should be helping out by judging ;). Events will be constructed as a combination of puzzles and real-world tasks, meaning some things will simply test your PowerShell skills, while others will test them in a more production-applicable way.
This post comes to us from Julie Andreacola, one of the members of team Kitton Mittons, who won The Scripting Games - Winter 2014. You’re welcome to submit your thoughts about the Games as well!__ The 2014 Scripting Games are over and once again, it was a terrific experience. This was my third scripting games and I was blown away with all that I learned. The team approach was very appealing to me as I have been the PowerShell expert at my workplace so I was hoping to find a team where someone knew more than I did as I’m only intermediate in PowerShell skills.
The judging is complete for the fourth and final event in the 2014 Winter Scripting Games. This Games was something very different in that we presented 4 we complex scenarios that were designed to be as close as possible to the type of tasks you may have to perform at work. The solutions required multi-file answers - there’s no way you could solve these with a one liner! All of the teams that submitted entries rose to meet the hardest challenge I’ve seen in a Scripting Games - and I’ve taken part of judged all but the first Games.
If you’ve been following along with The Scripting Games over the past couple of iterations, you know that we’ve been trying some different, new things. This Winter Games, we did a team-based series of events that threw some really complex scenarios at you. However, we know some folks would like to see the next Summer Games include a less-complex track that perhaps includes a focus on one-liners. (Not that one-liners are an essential part of a work environment, but they’re fun and a good competitive thing - this is games, after all.
There are a number of different ways to test for the presence of a registry key and value in PowerShell. Here’s how I like to go about it. We’ll use an example key HKLM:\SOFTWARE\TestSoftware with a single value Version: Click here to be redirected to the original post of this article on the author’s blog site where you can read the remainder of the article.
Try adjusting your search terms or browse all content.