xxxi
P
owerShell, VBScript,
and JScript Bible is a work in progress, just like the Windows operating
system itself and the body of work that’s grown up around it. It is quite likely that errors
will make themselves apparent after this book has gone to press and found its way onto
your desktop. I very much appreciate the efforts of readers who go to
the trouble of pointing out
mistakes in the text so I can fix them in future editions. Even more, I am grateful for readers who
offer their own hints, tricks, code, and ideas to me for inclusion in future editions of this book.
I truly hope you find that
PowerShell, VBScript and JScript Bible provides everything you need
to perform essential scripting tasks. You can contact me through e-mail at
williamstanek@aol
.com
. You’re always welcome to write me with ideas, suggestions,
improvements, or questions.
If you provide an example that’s used in a future edition of this book, I’ll be especially grateful
for your help and will credit you in that edition. I also have a Web site, which contains support
material
for this book, among other things. Point your browser to
www.williamstanek.com/
scripting/
for corrections, enhancements, news, and additional thoughts. I’ll post the source
code from this book as well.
Thank you!
William R. Stanek
The best introduction to a book I ever saw was from Machiavelli’s
The Discourses, where he says
something like, “I’m
sending you something, and if it doesn’t meet the obligations I owe you, is at
any rate the best I can send. For in it I have set down all I know from long experience and con-
stant reading…you may perhaps lament my lack of skill should my narratives be thin and also
errors of judgment if I have made mistakes.”
The longer the piece that I write, the more likely I am to think of that.
The experience I have in
PowerShell builds on decades of seeing different scenarios and using different tools: and that
experience has been gained working with people who don’t think of themselves as Programmers.
Graphical management tools make it easy to find how to do a one-off task, but some repetitive
tasks aren’t efficient with the GUI. Some information can’t be extracted easily from a graphical
tool: some tasks just weren’t anticipated by the Programmer who wrote it. UNIX system admin-
istrators have known for a long
time that there is an area, which isn’t Programming in the custom-
ary sense, of creating a large beast, with considerations such as user interface design to be taken
into account. It produces something that a dictionary would define as a program—a sequence of
instructions to be followed by the computer. A script is a program but not a Program (the capi-
talization is deliberate). Scripts are written mostly by
people who are not Programmers, but just
know the job they need to get done. And, usually a script will involve less time to create than a
“proper” Program and will pay back the time that went into it very quickly. Want to know which
86804flast.indd xxxi
86804flast.indd xxxi
1/22/09 11:52:15 AM
1/22/09 11:52:15 AM