Book Image

Mastering Windows PowerShell Scripting (Second Edition) - Second Edition

By : Brenton J.W. Blawat
Book Image

Mastering Windows PowerShell Scripting (Second Edition) - Second Edition

By: Brenton J.W. Blawat

Overview of this book

PowerShell scripts offer a handy way to automate various chores. Working with these scripts effectively can be a difficult task. This comprehensive guide starts from scratch and covers advanced-level topics to make you a PowerShell expert. The first module, PowerShell Fundamentals, begins with new features, installing PowerShell on Linux, working with parameters and objects, and also how you can work with .NET classes from within PowerShell. In the next module, you’ll see how to efficiently manage large amounts of data and interact with other services using PowerShell. You’ll be able to make the most of PowerShell’s powerful automation feature, where you will have different methods to parse and manipulate data, regular expressions, and WMI. After automation, you will enter the Extending PowerShell module, which covers topics such as asynchronous processing and, creating modules. The final step is to secure your PowerShell, so you will land in the last module, Securing and Debugging PowerShell, which covers PowerShell execution policies, error handling techniques, and testing. By the end of the book, you will be an expert in using the PowerShell language.
Table of Contents (24 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Assemblies


.NET objects are implemented within assemblies. An assembly may be static (based on a file) or dynamic (created in memory).

Many of the classes we might commonly use exist in DLL files stored in %SystemRoot%\Assembly. The list of currently loaded assemblies in a PowerShell session may be viewed using the following statement:

[System.AppDomain]::CurrentDomain.GetAssemblies()

Once an assembly, and the types it contains, has been loaded into a session, it cannot be unloaded without completely restarting the session.

Much of PowerShell is implemented in the System.Management.Automation DLL; details of this can be shown using the following statement:

[System.Management.Automation.PowerShell].Assembly

In this statement, the type PowerShell is chosen to get the assembly. Any other type in the same assembly is able to show the same information. The PowerShell type could be replaced with another in the previous command, for example:

[System.Management.Automation.PSCredential].Assembly 
[System...