<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Comment-Based Help on PowerShell.org - Welcome Automaters!</title><link>https://powershell.org/tags/comment-based-help/</link><description>Recent content in Comment-Based Help on PowerShell.org - Welcome Automaters!</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 Nov 2020 18:53:35 +0000</lastBuildDate><atom:link href="https://powershell.org/tags/comment-based-help/index.xml" rel="self" type="application/rss+xml"/><item><title>Writing Your Own PowerShell Functions / Cmdlets</title><link>https://powershell.org/articles/2020-11-05-writing-your-own-powershell-functions-cmdlets/</link><pubDate>Thu, 05 Nov 2020 18:53:35 +0000</pubDate><guid>https://powershell.org/articles/2020-11-05-writing-your-own-powershell-functions-cmdlets/</guid><description>&lt;p&gt;This article is an attempt at describing some of my thought process when building functions. By functions I mean a command that you can execute after importing a module. I am not referring to running a script that accepts parameters and input. Having a task to complete for a function is of course the first objective. Once an idea is in mind I like to write as much as the Help section first as possible as this helps me outline and plan what I am going to do.&lt;/p&gt;</description></item></channel></rss>