In CLM .ps1 files don't work as RootModule, NestedModules, or ScriptsToProcess in Module Manifests

[joshcorr]

Prerequisites

• Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
• Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Typo in Get-Foo cmdlet" instead of "Typo."
• Verify Version: If there is a mismatch between documentation and the behavior on your system, ensure that the version you are using is the same as the documentation. Check this box if they match or the issue you are reporting is not version specific.

Links

• https://learn.microsoft.com/en-us/powershell/scripting/developer/module/how-to-write-a-powershell-module-manifest?view=powershell-7.6
• https://learn.microsoft.com/en-us/powershell/scripting/developer/module/how-to-write-a-powershell-module-manifest?view=powershell-5.1
• all Versions

Summary

In the Module Manifest documentation there is no note that .ps1 files fail to load when the user is running in Constrained Language Mode (CLM).

Details

This issue came up while I was working on my talk for PowerShell & DevOps Summit as well as when I was making the UseConstrainedLangaugeMode PSScriptAnalyzer rule UseConstrainedLanguageMode.md

Suggested Fix

Include a note about the behavior change for CLM

[sdwheeler]

@joshcorr Thanks for the info.