If you are creating cmdlets or providers - definitely programming.
If you are using cmdlets & PowerShell language - definitely scripting
If you are accessing .Net - I would tend to say scripting if you are looking
to perform administrative tasks because (a) you've probably copied the script
from somewhere else and (b) its not that difficult. If you start getting to
the point on accessing SQL databases or web services then I would say
programming
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog:
http://richardsiddaway.spaces.live.com/
PowerShell User Group:
http://www.get-psuguk.org.uk
"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?
>
> Marco
> RedHat Certified *Engineer*
> ;-)
>
>
>