Powershell Oneliner Contest 2015 - Win a Hyper-V book

I have always enjoyed taking part in most of the Powershell contests out there since Powershell is kind of a recreational administration language to me. I am thinking, for example, of the fun I had taking part in the oneliner contest (which I won) organized by fellow MVP Mike F Robbins, or of the Powershell Golf organized in 2013 by Robert Robelo on Twitter.

 

THE IDEAS BEHIND THE CONTEST

 

Being quite proud of my blog, and despite the fact that I am more of a system administrator than a developer, I have unilaterally decided to organize my self-hosted, self-managed Powershell Oneliner Contest.
 

The three ideas behind this game are that:

1. experienced competitors (and I, of course!) should come away with a lot of tips from the brightest Powershell minds that will hopefully take part in the event
2. novice Powershell scripters should learn that persistence pays off when looking for a solution to such a contest
3. this is a fairly good occasion to sharpen your skills for the soon-to-start Powershell Scripting Games held by the Powershell.org community

GENERAL RULES
 

• The contest is split into three tasks. Each task consists of a simple scenario for which you have to produce a oneliner solution.
• Submit your solutions via a comment to this blog article by 11AM (PDT) on Wednesday, July 1st, which is the deadline.
• You MUST submit only one task solution per comment, so that I can easily see who was the first to submit the shortest solution on a per-task basis.
• Should you find a shorter oneliner to solve a task you are allowed to post additional comments (just remember to sign your comments so that I know who's who).
• Aliases are of course accepted
• Backticks accepted for readability
• No semi-colons
• UPDATE - No Here-String
• UPDATE - Please don't sign your comments as Unknown or I won't be able to know who you are.
• If you use a Powershell version other than v4, I am okay with it, but please mention it in the comment so that I can test it on the same version. Powershell v5 is welcome.
• Entries (comments) will not be made public until after the submission deadline.

SCORING

• The shortest solution in terms of chars wins.
• The first person to produce the shortest working solutions to a task will get 1 point, the second 2 points, the third 3 points and so on.
• The person with the lowest total score over the three mandatory tasks will be the winner.
• The winner will be announced on Saturday, July 4th on this blog and the prize will be awarded at that time.
• I'll be the only judge.

THE PRIZE

 

What? Is there a prize? Yes, of course. The prize will be a printed copy of the excellent book 'Hyper-V Best Practices' (5-Stars on amazon.com) by fellow MVP Benedict Berger  (@Benedict_Berger) offered by Packt Publishing!!!

I was the reviewer of the book as well of the ton of Powershell code it contains. I can tell you this is the book to read in these Hyper-V times!

As a bonus, and if the winner agrees, he/she will intervene as a guest blogger on this blog and will explain how one goes about learning the hidden bits of Windows Powershell. Sounds cool, doesn't it?

Let's now dive into the contest tasks.

 

TASK 1 - Who's taller?

 

This is a rather easy challenge and I hope it will make for a good warm-up session for your Powershell muscles, especially if you are a beginner. Given a $n variable showed below, write the shortest possible oneliner that outputs the absolute value of the largest double-precision floating-point number in the array.

$n = -1,-2,-5,-8.9,'b',-9.11,-6,-3,-2,-9.1,-1,-1.4,'a'

Expected output

Task-specific rules

• The object in the output can be of any type
• UPDATE - The one-liner must work also with different values of $n

TASK 2 - Can you count to five?

Time to delve into something harder. Write the shortest possible Powershell oneliner that outputs the number 12345.

Expected output

 

Task-specific rules

• You are not allowed to use the digits 0 to 9 in your oneliner
• The object in the output must be of type Int32
• Your displayed output shouldn't contain any other char

TASK 3 - Powershell is the secret word

I hope that by this time you are enjoying the competition. It's time for the last hard task. Write the shortest possible Powershell oneliner that outputs the word 'PowerShell' starting from a text string composed only of uppercase Xs' and whitespaces.

Expected output

Task-specific rules

• The string composed of X's and whitespaces must be part of the oneliner (backticks accepted!) and not be a variable defined on a separate line
• You can use as many X's and empty spaces you like or need
• P and S in the output must be uppercase
• UPDATE - No Here-String
• UPDATE - I consider jokes answers like "X "|%{"Powershell"}

On your marks, set, go! And remember to have fun, it's just a game meant to produce something useful for the growing and growing Powershell community!

UPDATE - Check-Task Function

I have decided to update this blog post with a function that will allow you to check if your proposed solutions are correct in terms of output and respect the task assignments. Kudos for this function go to my friend Joey!

function Check-Task ([int] $Task, [scriptblock] $Command) {
        $n = -1,-2,-5,-8.9,'b',-9.11,-6,-3,-2,-9.1,-1,-1.4,'a'
        $result = & $command
        $check = $false
        switch ($Task) {
            1 { $check = $result -eq '1.4' -or 
                [double]::Parse("$result") -eq 1.4 }
            2 {
                $check = ($result -is [int] -and $result -eq 12345) -and
                    ("$Command" -notmatch '[0-9]')
              }
            3 {
                $check = ($result -is [string] -and $result -ceq 'PowerShell') -and
                    ("$Command" -match '([''"])[X`\s]+\1')
            }
        }
        if (!$check) {
            Write-Host -Fore Yellow "Expected: $((1.4,12345,'PowerShell')[$Task - 1])"
            Write-Host -Fore Red    "Actual:  $result"
        }
        $color = ('Red','Green')[$check]
        Write-Host -Fore $color ('{0,4}: {1}' -f "$Command".Trim().Length,$command)
    }

Sample usage:

Check-Task 1 { $n.gettype() }

Do not hesitate to test your solutions before posting them to my blog! Better safe than sorry.

SPREAD THE WORD

If you want to give some visibility to this contest, feel free to twit about it. You can use the hashtags #poshcontest2015 and #powershell so that other competitors can share their thoughts (not the solutions of course!).

Thanks again to Packt Publishing (and to Mary in particular) for sponsoring this event!

UPDATE: Click here to find the winner's name and his solutions!