PSCore6 should have a way to use Windows PowerShell PSModulePath #4056
Description
Metadata
Metadata
Assignees
Labels
PS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifThe issue is fixed.The issue is fixed.
Type
Fields
Give feedbackNo fields configured for issues without a type.
With moving to .Net Std 2.0 and the PR to enable PSCore6 to load assemblies from the GAC, the missing piece to enable PSCore6 to replace the need for Windows PowerShell (majority of scenarios anyways) is to make it simpler for users to find and use in-box Windows modules. Currently, PSCore6 has no knowledge of the legacy Windows PowerShell PSModulePath. Since we know we don't have 100% compatibility with in-box modules (PSSnapIns, for example are not supported at all), it seems we should consider an opt-in approach. Alternatively, maybe we should have a
Windows Compatmodule that has a whitelist of validated modules that work with PSCore6?cc @joeyaiello @HemantMahawar