re: Learn When to Write PowerShell Scripts and When Not To

ScriptingGuy1 — Mon, 06 Dec 2010 11:33:31 GMT

@russ You should write a PowerShell script when you anticipate the need to run the command on more than one occassion. You should write a script if the command is very long and complicated (for me this is a command that takes up more than two lines in the PowerShell console). There are a few exceptions. If a command is a simple PowerShell cmdlet (stop-computer) then I do not put that in a script. In addition, most WMI commands are short enough for me not to mess with. For example I have yet to write a script to retrieve the bios (gwmi win32_bios). If on the other hand, I had a need for a sorted list of unique processes, and I wanted a particular style of output I might put that in a script. Keep in mind, that at its most basic, a script is just a collection of commands you might otherwise type in the console.

re: Learn When to Write PowerShell Scripts and When Not To

russ — Mon, 06 Dec 2010 10:59:54 GMT

Hi Ed,

can you clearly summarise When to Write PowerShell Scripts and When Not To please ?