On Mon, 12 Feb 2007 14:02:46 -0400, 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*
> ;-)
I think I would agree with this interpretion. If you are using cmdlets,
aliases and user defined functions to carry out administrative tasks, I
think it's safe to assume you are doing administrative scripting. To my
mind, it becomes more of a gray area once you start invoking .NET code and
stuff from within PowerShell. Then I feel you need an understanding of
..NET and have moved from script type automation, to more programming.
--
Jeffery Hicks
SAPIEN Technologies - Scripting, Simplified.
www.SAPIEN.com
VBScript & Windows PowerShell Training -
www.ScriptingTraining.com/classes.asp
Windows PowerShell? -
www.SAPIENPress.com/powershell.asp
blog:
http://blog.SAPIEN.com
blog:
http://jdhitsolutions.blogspot.com