So what I have done is I have created two separate "help" projects using the same module as a base. One will use Sapien powershell help writer to import the module, modify the help content of the functions, and generate the external help document. The external help file generated using this process has consistently just not worked, as attempting to view the help information for functions will simply display what I assume to be the default, bare-bones help content rather than what is actually present:
The other project will use platyps, a powershell module which is essentially the working, free alternative to Sapien powershell help writer to import the module, modify the help content of the functions, and generate the external help document. As mentioned previously, I have had far more success using platyps than I have using Sapien powershell help writer:
I am doing it this way for a few reasons. This way, you will get the help project, the module which was used to build it, the broken help file that it generates, and can compare the broken sapien help file to the working help file generated using platyps. This I would hope would make it easier to identify and quickly fix what is wrong with Sapien Powershell help writer. Another reason I am doing it this way is so that I can document here any....oddities....that I come across while trying to generate the external help file using Sapien powershell help writer, which I will start below:
***Oddities****
1. When I created the project fresh by importing the module to automatically generate the functions that would make up the help file, I noticed as I was going through the functions that at least one, as seen below, automatically had the name of the function populated in the "Synopsis" text box in Sapien powershell help writer:
