for systems administration or scripting ? Cause I differ between the two.
Of course, it's the
same cmdlets used in the end, but how you do things, differ a lot to me at
For scripting, I've thought of the same kind of list of "what you need to
know if you want to
script in powershell". But not based around cmdlets, but rather around:
- Error handling
- Flow control
- Data types/structures
- Script arguments/parameters
When you get more advanced:
- Output formatting
- Remoting (in v2)
- Progress indicators
I actually thought of doing a Best Practices with examples of the cmdlets
to go along. Which I
think would be a good idea no matter who wrote it.
My sincere belief is that if you just learn the cmdlets, you're learning
In my world at least, it's always been learn what task you need to complete,
then learn what
the tools to do it are.
That makes the cmd-lets "less important" (not that any of them are not important),
more on the concepts. And the concepts are what people can build upon, and
take with them to
other languages and platforms. When you got it right, it's more or less just
syntax you gotta learn
to apply it elsewhere.
In any circumstance - good initiative
I also thought of doing a wiki on the various cmdlets, with thorough and
and descriptions. To share, but also to work with them in detail and learn
Jacob Saaby Nielsen http://www.pipforhelvede.net
gmail: jacob DOT saaby
hotmail (IM/LinkedIN/Facebook): same as gmail
> I'm trying to compile a list of cmdlets that a complete beginner
> should know or at least will likely use during their first encounters
> with PowerShell.
> Now that's beyond get-help, get-command and get-member.
> Some examples:
> get-item, get-childitem
> copy-item, new-item, remove-item
> new-variable, remove-variable
> Again, just the most basics to get somebody started.