Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Windows PowerShell for .NET Developers - Second Edition
  • Table Of Contents Toc
  • Feedback & Rating feedback
Windows PowerShell for .NET Developers - Second Edition

Windows PowerShell for .NET Developers - Second Edition - Second Edition

By : Chendrayan Venkatesan, Talaat
Buy this Book
close
close
Windows PowerShell for .NET Developers - Second Edition

Windows PowerShell for .NET Developers - Second Edition

By: Chendrayan Venkatesan, Talaat
Buy this Book

Overview of this book

Windows PowerShell 5.0 for .NET Developers is your self-start guide to performing automation using Windows PowerShell. This book will help you to understand the PowerShell syntax and grammar and will also teach you techniques to remove the rough edges of manual deployments. Packed with PowerShell scripts and sample C# codes to automate tasks, it also includes real-world scenarios such as administrating office servers to help you save time and perform deployments swiftly and efficiently. The book begins with the Windows PowerShell basics, explores the significant features of Windows Management Framework 5.0, covers the basic concepts of Desired State Configuration and the importance of idempotent deployments. By the end of the book, you will have a good understanding of Windows PowerShell’s features and will be able to automate your tasks and manage configuration effectively.
Table of Contents (7 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Getting Started with Windows PowerShell
Icon
1. Getting Started with Windows PowerShell
Icon
Scripting the cmdlet style
Icon
Introducing Windows PowerShell
Icon
Using an interactive shell
Icon
Summary
2
2. Unleashing Development Skills Using Windows PowerShell 5.0
chevron up
Icon
2. Unleashing Development Skills Using Windows PowerShell 5.0
Icon
Basics of WMI and CIM
Icon
Working with XML and COM
Icon
Exploring .NET objects
Icon
Exploring Windows PowerShell 5.0
Icon
Understanding PowerShell modules
Icon
Script debugging
Icon
Summary
3
3. Exploring Desired State Configuration
Icon
3. Exploring Desired State Configuration
Icon
Prerequisites
Icon
Installing the WMF 5.0 April 2015 preview
Icon
Imperative versus declarative programming
Icon
Getting started with DSC
Icon
Exploring Windows Remote Management and CIM
Icon
Creating configuration scripts
Icon
Types of deployment modes
Icon
Summary
4
4. PowerShell and Web Technologies
Icon
4. PowerShell and Web Technologies
Icon
PowerShell Web Access
Icon
Management OData IIS Extensions
Icon
Exploring web requests
Icon
Exploring web services
Icon
Exploring the REST API
Icon
Exploring JSON
Icon
Summary
5
5. Exploring Application Programming Interface
Icon
5. Exploring Application Programming Interface
Icon
Exploring API using PowerShell
Icon
The Lync 2013 client-side API
Icon
Client-side object model – SharePoint Online
Icon
Summary
6
Index
Icon
Index

Understanding PowerShell modules

Windows PowerShell modules present a simple way to organize and package our script so as to make it distributable and reusable.

In this section, we will cover the following topics:

  • What is a module?
  • Script modules
  • Binary modules
  • Manifest modules
  • Dynamic modules

Introduction to modules

Windows PowerShell can be created dynamically or persisted to our disk. While discussing PowerShell modules, for a moment I thought about the old-style snap-ins in PowerShell version 1.0, which still exist. Yeah! SharePoint still has snap-ins and not modules.

Snap-ins only contain cmdlets and providers, whereas in modules, we can have functions, variables, aliases, and PowerShell drives.

Before we create a module, we need to know what a module should deliver and where it should be placed. Use this code to find the module path:

$env:PSModulePath -split ';'

You will see two different paths, where one is the system location and the other is the user profile location, as follows...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Windows PowerShell for .NET Developers - Second Edition
End of Section 2
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon