Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn PowerShell Core 6.0

You're reading from   Learn PowerShell Core 6.0 Automate and control administrative tasks using DevOps principles

Arrow left icon
Product type Paperback
Published in Jul 2018
Publisher Packt
ISBN-13 9781788838986
Length 552 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Authors (2):
Arrow left icon
David das Neves David das Neves
Author Profile Icon David das Neves
David das Neves
Jan-Hendrik Peters Jan-Hendrik Peters
Author Profile Icon Jan-Hendrik Peters
Jan-Hendrik Peters
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Current PowerShell Versions FREE CHAPTER 2. PowerShell ISE Versus VSCode 3. Basic Coding Techniques 4. Advanced Coding Techniques 5. Writing Reusable Code 6. Working with Data 7. Understanding PowerShell Security 8. Just Enough Administration 9. DevOps with PowerShell 10. Creating Your Own PowerShell Repository 11. VSCode and PowerShell Release Pipelines 12. PowerShell Desired State Configuration 13. Working with Windows 14. Working with Azure 15. Connecting to Microsoft Online Services 16. Working with SCCM and SQL Server 17. PowerShell Deep Dives 18. PowerShell ISE Hotkeys 19. Assessments 20. Other Books You May Enjoy

Chapter 5

  1. It lets a function behave like a compiled cmdlet, thus giving it access to common parameters, such as Verbose and ErrorAction
  2. ParameterSetName
  3. One from: SYNOPSIS, DESCRIPTION, PARAMETER, EXAMPLE, NOTES
  4. Using signed code in RemoteSigned and AllSigned mode will not trigger the execution policy
  5. Manifest (psd1) and script module (psm1)
  6. PowerShell examines $env:PSModulePath for valid folder structures containing module files and then imports all exported cmdlets, functions, variables, aliases, and so on
  7. Source control system
  8. To more easily revert changes and have a more granular history of changes
  9. To develop code independently from others
  10. Static code analysis, for example, proper indentation, style, disallowed aliases, and more
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image