Windows PowerShell实战指南

需积分: 10 4 浏览量更新于2024-07-26 收藏 6.83MB PDF 举报

《PowerShell实战指南》（Windows PowerShell in Action）是由Bruce Payette和Manning共同编著的一本专业IT技术书籍，专注于介绍Windows PowerShell在实际操作中的应用。本书是针对Windows PowerShell这一强大的命令行工具，旨在帮助读者深入理解其核心概念、语法结构以及如何高效地管理和自动化Windows系统任务。 PowerShell是Microsoft推出的一种基于.NET框架的脚本语言，它将管理任务整合到了一个统一的环境中，能够简化和增强Windows系统的管理和维护。本书通过实例演示和深入剖析，让读者能够快速上手，无论是系统管理员、开发者还是对自动化运维感兴趣的用户都能从中受益匪浅。书中内容涵盖了PowerShell的基础知识，如变量、命令、管道、模块和函数等，同时还会涉及更高级的主题，如模块化编程、错误处理、脚本设计和调试，以及与Windows API的交互。作者强调了PowerShell在服务器管理、配置管理、网络操作、文件操作和安全控制等方面的应用，使读者能够在日常工作中灵活运用。值得注意的是，该书还讨论了PowerShell版本之间的差异，如从Windows XP到Windows 10的变迁，以及不同版本的特性和兼容性问题。此外，书中还提供了大量的实战案例和最佳实践，帮助读者提升在复杂环境下的解决问题能力。对于购买和获取资源的方式，读者可以在Manning出版社的官方网站www.manning.com上查找并享受批量订购的优惠。如果需要进一步的信息或有疑问，可以直接联系Manning出版社的特别销售部门，通过电话（609-877-8256）或电子邮件（orders@manning.com）进行交流。版权方面，本书享有Manning Publications Co.的完整版权，未经出版商事先书面许可，任何形式的复制、存储、检索或传输都是不允许的。此外，书中提及的制造商和销售商的商标已按照相应的知识产权规定标注。《PowerShell实战指南》是一本实用的IT技术参考书，对于提高Windows PowerShell技能，实现系统管理的自动化和效率提升具有极高的价值。无论你是初学者还是进阶者，阅读这本书都能助你在PowerShell的世界里游刃有余。

foreword

Windows PowerShell has the widest range of any language I know. You can quickly learn the

basic concepts and use it as an interactive command line shell to write simple, ad hoc scripts.

Learn a bit more and you can use it to write rich, sophisticated scripts to manage your most

important production servers. Learn a bit more still, and you can write .

NET programs to access

the awesome power of the .

NET frameworks.

When we started to develop PowerShell, I was advised to deliver an interactive shell or script-

ing language and to avoid .

NET programming, because C# and VB.NET had that covered. This

had been the standard approach of every

OS in the last 30 years. I knew that we could do better.

A new architecture based upon a deep rethink of the problem to provide our customers with a

single solution which would do the following:

• Allow beginners a quick start and the ability to become advanced users over time, enhanc-

ing their careers and salary potential.

• Let advanced users use it in lightweight, ad hoc ways for simple problems and in sophisti-

cated, production-oriented ways for complex problems.

• Create a large community of beginners and advanced users to share experiences,

approaches, and scripts.

• Create a large ecosystem which would increase the opportunities for job hunters as well as

increase the hiring pool for employers.

Designing and implementing a solution that could do all that was challenging. At times, we had

to make some difficult choices, but we were on a mission and we stuck to our vision. This is

where Bruce Payette comes in. Bruce is a founding member of the PowerShell team and the

development leader of the PowerShell language. I paired Bruce with Jim Truher, a Program Man-

ager (

PM) and another founding member of the team. As a PM, Jim was the advocate for the user

and the voice of sanity. Bruce and Jim worked incredibly well together, producing the PowerShell

language and addressing the many problems that came up. Bruce is a walking encyclopedia of

every good, bad, solid, and wacky language idea that has been tried in the last few decades. As

issues came up, Bruce explained how the different languages addressed similar issues, where and

why they worked well, or failed. Bruce was crucial in solving the problems we encountered and

in fulfilling our ambitious goals.

xvii

preface

Wow, I wrote a book! How the heck did that happen? One moment you’re a humble program-

ming language designer, and the next you’re up until 2 a.m. every night trying to figure out how

to say “and in the next example” 500 times without being boring.

So why write it? Because of PowerShell. Although PowerShell draws heavily from existing tech-

nologies, it combines them in novel ways. This novelty leads to misunderstandings, which then

turn into urban myths, such as, PowerShell does

X because its designers are kitten-eating aliens.

Trust me–we’re not.

As we showed our work to the world (three public betas and two release candidates), I found

that there were a few questions that were being asked over and over again. These questions would

arise as a result of an earlier language experience that the user had had. Typically, a simple expla-

nation was all it took to clear up the confusion (we had a very smart group of beta testers). How-

ever, we couldn’t keep answering these questions one-by-one; that just wouldn’t scale. There

needed to be a way to gather the information in one place. This book is my attempt to do just that.

The other astonishing thing was just how much power comes out of the synergy of the tech-

nologies underlying PowerShell. We saw this in our own internal uses of PowerShell as well as

in some of the community examples. The PowerShell team read people’s blogs and was astonished

by the creativity that was being demonstrated. So the second goal of this book is to foster that

creativity by conveying how capable PowerShell is.

Finally, this is the book I had always wanted to read myself. I love programming languages and

reading about them, and the best programming books I found are the ones that explain not only

“what” but also “why.” Look at the books that continue to sell year after year, like Kernighan and

Ritchie’s The C Programming Language, Stroustrup’s C++ book, and Ousterhout’s

TCL book. The

TCL book is a very good example: it describes an early version of the TCL language, it has never

been updated, yet it continues to sell. Why? This book, and others like it, give the reader some-

thing more than just technical detail. They convey a sense of the overall design as well as some

of the intent of the designer. So please let me know if you think I succeed in doing that with this

book,

OK?

The very last goal of the book was to help build and maintain momentum around PowerShell.

PowerShell was released around the time of Microsoft’s biggest product release ever: the revamped

operating system Vista together with the new Office suite (with all those wild graphical

3D doo-

hickeys added everywhere). But we’re just a command line. There is a good rule to follow when

xix

acknowledgments

This book is for my wife, Tina. It literally wouldn’t exist without her patience, support, and

encouragement. She kept me fed, sane, and she even read early drafts of material about which she

knows nothing. Now that’s support! She also contributed the Gnome picture in chapter 13 and

the bird-watching information and pictures in chapter 2.

Thanks to my parents for their love and support over the years. Yes, I am finally done with

the book.

Of course there wouldn’t be a PowerShell book without a PowerShell product in the first place,

and PowerShell wouldn’t exist without the vision of its chief architect, Jeffrey Snover. Special

thanks to Jeffrey for reviewing the mansucript and for agreeing to write the foreword to the book.

Another other major contributor was Jim Truher, my co-conspirator in the PowerShell lan-

guage design. Yes, it’s our fault.

I’d like to thank the rest of PowerShell language team: George Xie, Marcel Ortiz Soto (test-

dude extraordinaire), and Wei Wu, all of whom contributed enormously to the project. Kaushik

Pushpavanam, one of the original PowerShell team members, gets major props for introducing

a unit test framework into the PowerShell development process early and then getting the devel-

opers to use it and write tests. This gave us the freedom and agility to listen to customers and

incorporate changes throughout the development process. Thanks to Hilal Al-Hilali for knowing

how to ship; he’s a mean man with a theme. Thanks to Charlie Chase for winning. PowerShell

team members Arul Kumaravel and Abhishek Agrawal contributed significantly to the

COM and

WMI examples in chapter 12. (Arul wrote the COM support, so who could have been better?)

Thanks also to all of the reviewers of the manuscript in its many stages of development: Jeffrey

Copeland, Arul Kumaravel, Rene Gobeyn, Jeffrey Snover, Steve Simmons, Keith Hill, Oliver

Sturm, Thomas Restrepro, Anil Radhakrishna, Alex K. Angelopoulos, David McMahon, Curt

Christianson, Anderson Patricio, Jon Skeet, and Robert. W. Anderson. A special thanks to Alex

Angelopolous who did the final technical review of the book. I’d also like to thank all of the par-

ticipants in the Manning Early Access Program. You guys rock! Much appreciation to everyone

at Manning, starting with my publisher Marjan Bace, my editor Michael Stephens, my develop-

ment editors Betsey Henkels and Jackie Carter, and all the production staff for their hard work

and patience with a new author.

Finally, I want to thank my friend and mentor David Tillbrook for never being satisfied with

the merely adequate. He has a lot to teach us all.

剩余575页未读，继续阅读

zhangboo800320

粉丝: 5

Windows PowerShell实战指南

Windows PowerShell in Action.Third Edition

Windows PowerShell in Action(2nd) 无水印pdf

Windows Powershell in Action

windows powershell in action third edition

Windows PowerShell in Action, Second Edition

Windows PowerShell in Action Errors, Updates and Clarifications

Windows PowerShell in Action by Bruce Payette

Windows PowerShell in Action修订与解答

Windows PowerShell in Action：深入脚本编程指南

Manning.Windows.PowerShell.in.Action

最新资源