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
get-content,add-content
stop/start-process
stop/start-service
get-eventlog
measure-object
write-host
set-location
copy-item, new-item, remove-item
new-variable, remove-variable

Again, just the most basics to get somebody started.

Comments?

Marco

Set-Content
Get/Set-ItemProperty

-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

> 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
> get-content,add-content
> stop/start-process
> stop/start-service
> get-eventlog
> measure-object
> write-host
> set-location
> copy-item, new-item, remove-item
> new-variable, remove-variable
> Again, just the most basics to get somebody started.
>
> Comments?
>
> Marco
>

Format-Custom
Format-List
Format-Table
Format-Wide

-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

> 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
> get-content,add-content
> stop/start-process
> stop/start-service
> get-eventlog
> measure-object
> write-host
> set-location
> copy-item, new-item, remove-item
> new-variable, remove-variable
> Again, just the most basics to get somebody started.
>
> Comments?
>
> Marco
>

Hey Marco,

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
least.

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:

- Modularity
- Error handling
- Flow control
- Data types/structures
- Input/Output
- Script arguments/parameters

When you get more advanced:

- Output formatting
- WMI
- Remoting (in v2)
- Progress indicators

.... etc.

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
backwards.
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),
and focuses
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
explanatory examples
and descriptions. To share, but also to work with them in detail and learn
myself.

Best Regards,
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
> get-content,add-content
> stop/start-process
> stop/start-service
> get-eventlog
> measure-object
> write-host
> set-location
> copy-item, new-item, remove-item
> new-variable, remove-variable
> Again, just the most basics to get somebody started.
>
> Comments?
>
> Marco
>

> stop/start-process
start-process - a mistake? There is no such a cmdlet or at least it is not
"standard".

--
Thanks,
Roman Kuzmin

http://code.google.com/p/farnet/
PowerShell and .NET in Far Manager

Roman Kuzmin wrote:

>> stop/start-process

> start-process - a mistake? There is no such a cmdlet or at least it is
> not "standard".
>

You're right, a mistake on my part.

Marco

"Roman Kuzmin" <z@xxxxxx> wrote in message
news:58C97283-655F-4D58-AE4C-4369241BF7D9@xxxxxx

>> stop/start-process

> start-process - a mistake? There is no such a cmdlet or at least it is not
> "standard".

There is a Start-Process cmdlet in PSCX.

--
Keith
http://www.codeplex.com/poweshellcx

I gotta say ... I don't see these as "complete beginner" cmdlets that
you'd use in your first couple encounters...

> stop/start-process
> stop/start-service
> get-eventlog
> new-variable, remove-variable

I'm pretty sure I've never used Get-EventLog, and the only place I've
ever used New-Variable is in scripts (don't most of us usually define
variables with $variable = ex?) and as someone else said below, stop/
start-process are part of PSCX --which I find invaluable, but wouldn't
necessarily consider necessary for the complete beginner

What about Format-Table/List/Wide, and Select-Object?

Joel (Jaykul) Bennett wrote:

> I gotta say ... I don't see these as "complete beginner" cmdlets that
> you'd use in your first couple encounters...

Thanks for the input. Perhaps, "beginner system administrators"? I do
think get-eventlog is a good cmdlet to use to show some of the power of
PSH for somebody new.

Marco

Marco Shaw [MVP] wrote:

> 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.

gwmi
%
?
select-object
select-string


--

Hal Rottenberg
Blog: http://halr9000.com
Webmaster, Psi (http://psi-im.org)
Co-host, PowerScripting Podcast (http://powerscripting.net)