Marco Shaw wrote:
> Was looking through something recently, and it refered to "PowerShell
> programming" as doing 'regular stuff' with PowerShell like writing .ps1
> *scripts*... Now, I would associate programming with one writing extensions
> to PSH using something like C# or VB.NET. As for someone just doing 'plain
> old script', I'd think we'd still call them scripters?
I'm just going to toss my two cents in here... If I'm just doing simple
stuff like moving files, calling cmdlets, conditional looping, counting,
reformatting, automating, etc., that's scripting to me. Unfortunately,
I find that most of the "power" in Powershell is buried in the
Get-WmiObject cmdlet. As soon I go digging around with Get-WmiObject
and have to start figuring out methods and properties, I consider myself
deep in programmer territory without a DotNET helmet.
--Jonathan "smthng" Kalmes
http://smthng.info