re: Add Code Snippets to Your Script by Using the PowerShell ISE

IamMred — Fri, 18 Feb 2011 21:45:06 GMT

In the previous article, blogs.technet.com/.../use-powershell-to-download-and-install-internet-code-snippets.aspx I talk about 3rd party editors (I specifically mentioned PowerGUI) and how they have support for real code snippets. I also have links to the XML Schema on MSDN for such snippets. But what I am specifically trying to do here, is to provide a way for a regular IT Pro to easily be able to grab and use snips of code that they may create themselves. The previous article also talks about registering a file extension with an application, and is useful even if one does not create a .snip file. In fact, the entire four articles are more an exploration of how one might approach a particular problem. It certainly is not a complete solution, although it can be used to solve a real problem without involving additional software. I appreciate you commenting on the blog, and helping to keep me focused on the reader. In fact, I am glad for your comments because they point out a different perspective.

re: Add Code Snippets to Your Script by Using the PowerShell ISE

Poshoholic — Sun, 13 Feb 2011 19:46:32 GMT

I think it's a shame that you write this series talking about code snippets, which are incredibly powerful and useful, without any mention that what you are really doing here is providing a workaround or a stop-gap measure in the PowerShell IDE to much richer true code snippet functionality, and that this functionality is supported in many modern IDEs and in richer PowerShell script editors that are available today for free (PowerGUI) or in commercial format (PowerGUI Pro, PowerShell Plus, Primal Script, etc). Many of your readers won't have an idea what code snippets found in modern IDEs really are since they won't have the developer background, and they may be new to PowerShell/scripting, and this series is teaching them about snippets incorrectly, introducing yet another extension (.snip instead of .snippet), with a different file format (text instead of xml), with no mention of the real power that is available in true code snippets. Maybe I'm too much of a purist, but I think that you're really doing your readers a disservice without explaining this properly in these articles.