Option 1: Packaging a module for targeting multiple versions and multiple editions of PowerShell Packaging options with logic for loading proper DLLs. ModulesĬan have two sets of compiled DLLs targeting both CoreCLR and FullCLR. Required logic in either RootModule or in the module manifest using $PSEdition variable. Module authors can publish a single module targeting to either or both PowerShell editions (DesktopĪ single module can work on both Desktop and Core editions, in that module author has to add # Find modules supported on PowerShell Core editions # Find modules supported on PowerShell Desktop edition Modules without PSEdition_Desktop and PSEdition_Core tags are considered to work fine on Using tags PSEdition_Desktop and PSEdition_Core. PowerShell Gallery users can find the list of modules supported on a specific PowerShell Edition Outside of this scenario, the value is only used as metadata. Get-Module -ListAvailable -PSEdition Core | % CompatiblePSEditionsīeginning in PowerShell 6, the CompatiblePSEditions value is used to decide if a module isĬompatible when modules are imported from $env:windir\System32\WindowsPowerShell\v1.0\Modules. Get-Module -ListAvailable -PSEdition Desktopĭirectory: C:\Program Files\WindowsPowerShell\Modules When getting a list of available modules, you can filter the list by PowerShell edition. TypeName: ĬompatiblePSEditions Property CompatiblePSEditions $ModuleInfo | Get-Member CompatiblePSEditions \TestModuleWithEdition.psd1 -CompatiblePSEditions Desktop,Core -PowerShellVersion 5.1 Variable, it can not be imported on PowerShell v4 or lower. Once a module manifest is specified with the CompatiblePSEditions key or uses the $PSEdition
0 kommentar(er)
