loading...
HassleFree Solutions, LLC.

Hello World in PowerShell

4lch4 profile image Devin W. Leaman Updated on ・3 min read

The following is a blog post I wrote for The Renegade Coder's sample-programs repository.

PowerShell Background

PowerShell is the de facto scripting language for managing Windows machines/servers. Microsoft has made it quite clear that PowerShell is here to stay and will become the preferred way to manage Windows servers in the future.

Jeffrey Snover is largely credited as the designer behind the language, while Bruce Payette and James Truher were also on the project, and in an interview in 2017, Snover explained the motivation behind creating PowerShell:

I'd been driving a bunch of managing changes, and then I originally took the UNIX tools and made them available on Windows, and then it just didn't work. Right? Because there's a core architectural difference between Windows and Linux. On Linux, everything's an ASCII text file, so anything that can manipulate that is a managing tool. AWK, grep, sed? Happy days!

I brought those tools available on Windows, and then they didn't help manage Windows because in Windows, everything's an API that returns structured data. So, that didn't help. [...] I came up with this idea of PowerShell, and I said, "Hey, we can do this better."

Originally, PowerShell was to be called Monad and it's ideas were published in a white paper titled Monad Manifesto. Shortly after releasing the Beta 3 version Microsoft formally renamed Monad to Windows PowerShell, followed by the release candidate 1 version.

PowerShell is now up to version 5.1 for stable builds and the new 6.0 version which was announced in 2016 is in public beta. The largest change in this version is it's now open-source and will now be called PowerShell Core as it runs on .NET Core as opposed to the .NET Framework which previous versions use.

Hello World in PowerShell

Enough background, let's actually get something working 😊

Write-Host 'Hello, World!'

To execute this code, simply open a PowerShell console on any Windows machine as it comes installed by default. You'll see the reply output in the window like so:

Hello_World

As is the case with most modern scripting languages, getting a Hello World sample running is really easy.

How to Run the Solution

Instead of running the commands directly within the console though, the best route is to write your scripts in a file and call the file when necessary. Download a copy of the Hello-World.ps1 file from the repository and open a console.

Now, navigate to wherever you downloaded the script and execute it by calling it like so:

.\Hello-World.ps1

This calls the script and returns the output to the console:

Hello_World_Script

Posted on by:

4lch4 profile

Devin W. Leaman

@4lch4

Just another internet denizen who likes making things, usually with code.

HassleFree Solutions, LLC.

We're a group of developers and creators that create software we love for others to enjoy. We have a heavy focus on a pleasing and easy to use UX, as well as open sourcing as much of the code as possible.

Discussion

markdown guide
 

Sadly the script file won't run by default on Windows due to a security policy. To change the policy and subsequently run the script you need to do the following:

1 - Open Run Command/Console ( Win + R )
2 - Type: gpedit.msc (Group Policy Editor)
3 - Browse to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Windows Powershell.
4 - Enable "Turn on Script Execution"
5 - Set the policy as needed. I set mine to "Allow all scripts".

Source: google.com.do/search?q=enable+runn...