Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
PowerShell Troubleshooting Guide

You're reading from   PowerShell Troubleshooting Guide Minimize debugging time and maximize troubleshooting efficiency by leveraging the unique features of the PowerShell language

Arrow left icon
Product type Paperback
Published in Nov 2014
Publisher
ISBN-13 9781782173571
Length 206 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Michael Shepard Michael Shepard
Author Profile Icon Michael Shepard
Michael Shepard
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. PowerShell Primer FREE CHAPTER 2. PowerShell Peculiarities 3. PowerShell Practices 4. PowerShell Professionalism 5. Proactive PowerShell 6. Preparing the Scripting Environment 7. Reactive Practices – Traditional Debugging 8. PowerShell Code Smells Index

Parameter type transformation


PowerShell allows us to ignore the idea of variable types in most situations and this is a tremendous productivity boost. When you consider all of the different Common Language Runtime (CLR) types that are used in a typical script it's easy to see why not worrying about naming the types saves a lot of time. Adding in all of the anonymous types (for instance, results of a select-object call), the need for a very liberal typing system is obvious. One example when specifying types is useful, or even critical, is when specifying parameters to a function:

function get-dayofweek{
param($date)
  Write-Output $date.DayOfWeek
}

This function seems like it would work well, but testing it shows that it's not quite right, as shown in the following screenshot:

Since we didn't specify what type the parameter was, the problem was that the constant string '5/27/2014' was passed into the parameter as is, that is, as a string. Since the string didn't have a DayOfWeek property, the...

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