I certainly can and will do that as soon as I'm able to. In the meanwhile I'd like to share some observations with you regarding my module problem that I find to be quite curious. I downloaded the 45 day trial version of PowerShell Studio 2017 (for pre-procurement evaluation) I then created a new module utilizing the "New Module from Functions" feature. I made certain to enable the "Create external help file" option. I then imported the newly created module into PowerShell Studio 2017 and Voilà PowerShell Studio Primal Sense works flawlessly. I also imported the newly created external help file into the Sapien Document explorer and Voilà Cmdlet help is displayed in its full glory. I removed the bad module from Primal Script, Cleared the PSPrimal Sense cache, restarted Primal Script, re-imported the module and Primal Script continues to exhibit the behavior that was originally reported. Thanks
I didn't find the right solution from the Internet.
victorgrant replied
396 weeks ago