Most organizations lack the resources to develop
special applications and utilities on their own and may struggle to accomplish more complex tasks using
available commands alone.
Another drawback shared by most shells is the way in which they handle information. The results of
running a command or utility is returned as text to the command line. If you need to use this text as
input for another command, which is common in scripting, it has to be parsed. Parsing is the process of
evaluating text and extracting the meaningful values in a form that can then be properly interpreted by
another command. Parsing is prone to error and can be time consuming because the format required for
preparing the textual input can vary greatly between different commands, applications, and utilities.
One final limitation to consider is the lack of integration between a shell and the scripting languages you
would use in that shell. For example, Windows Script Host provides a method for implementing a
variety of scripting languages from the command line (via cmd.exe ), but it is not integrated with
cmd.exe and is thus not interactive. It also lacks readily accessible documentation from the command
line as you would find in many other shells and scripting environments.
The Power Behind PowerShell
What sets Windows PowerShell apart from all other command shells is that it is built on top of .
Pages:
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33