Comment-based help is error-prone one typo in a keyword causes Get-Help to ignore the whole comment block, so I really rely on my tools, including this feature, to avoid errors. It parses my code and adds starter help, including help for my parameters. I jump in, write my function, add parameters, and then right-click and click Generate comment-based help. What’s less predictable is how often I use it. It’s predictable that I would love this feature. The Qualify Cmdlet Names feature ( Ctrl+Shift+H) is a great addition, too, especially with the proliferation of cmdlets and modules in open source. Before I share any script or function, or even a code sample, I press Ctrl + Shift + A, to replace all cmdlet, function, and parameter aliases with their correct full names. I’m a huge proponent of Windows PowerShell best practices, but like everyone else, my instinctive behaviors don’t always meet my coding standards. Do you have a different list? Share in the comments below.Īnd, don't miss the second installment of this article: Hidden Charms of PowerShell Studio #2. Here’s my list of can’t-live-without-’em features of PowerShell Studio. But, it’s the smaller, quieter features that have me hooked. MSI creation, the Function Builder and Parameter Builder, and New Module from Functions. I love the big powerhouse features, like PowerShell GUI automation. When I speak at conferences and user groups, I don’t typically talk about products, because people don’t want to hear “vendor talks.” But, in private, I’ve become a total PowerShell Studio fan-girl. and my one-year anniversary of using PowerShell Studio as my primary IDE. I’m coming up on my one-year anniversary at SAPIEN Technologies, Inc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |