32 or 64 bit version of product: 64-bit
Operating system: Windows 7 Pro
32 or 64 bit OS: 64-bit
PowerShell Version: 5
This morning I began building a new PowerShell module (project). After I created the module I used the "Build Module" button and after a short bit the module appeared in the Object Browser with the cmdlets. The cmdlets are not located in the module itself. I dot-sourced each cmdlet in it's own .ps1 under a subfolder. This worked fine.
# dot-source all function files Get-ChildItem -Path $PSScriptRoot\PSS\*.ps1 | Foreach-Object{ . $_.FullName } $RestrictedFunctions = "Test-ElevatedShell", "Get-ReturnCode" Export-ModuleMember –Function @(Get-Command –Module $ExecutionContext.SessionState.Module | Where-Object { $RestrictedFunctions -notcontains $_.name })I made a change to a couple of the cmdlets scripts this afternoon by renaming a couple of the parameters. I updated the version number in the .psd1 file for the module and then used the "Build Module" button again. After the update I was able to confirm the version of the module using GET-MODULE -ListAvailable. I confirmed the new parameter names were accessible from PSS and the console. The cache file names contained the new version number and the appropriate information was embedded in them.
What I discovered is that if I right click on the cmdlet under the Object Browser and select Show Help, the old "Syntax" and "Parameters" are displayed from the module I generated this morning. How does the Help get rebuilt / updated? By putting the cmdlets in their own .ps1 file and .dot sourcing them; does this break what PSS is able to read, after the initial Help is generated?