Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test-ModuleManifest fails in Core #353

Closed
Halkcyon opened this issue Apr 2, 2019 · 1 comment
Closed

Test-ModuleManifest fails in Core #353

Halkcyon opened this issue Apr 2, 2019 · 1 comment

Comments

@Halkcyon
Copy link

Halkcyon commented Apr 2, 2019

Related issue: PowerShell/PowerShell#6818

When trying to import Plaster in PowerShell Core 6.2, the Test-ModuleManifest call in Plaster.psm1 is failing, stating the manifest is invalid. I am able to remediate this interactively doing

Get-Module -ListAvailable -Refresh
Import-Module -Name Plaster -Force

but this remediation does not work when executed from my powershell profile.

Note: I could not replicate the behavior in Windows PowerShell 5.0.


My current workaround is modifying the psm1 to:

$PlasterVersion = [version](Import-PowerShellDataFile -Path $PSScriptRoot\Plaster.psd1)['ModuleVersion']

Environment Details

  • Windows 7 SP1 x64
  • PowerShell Core 6.2
@jdhitsolutions
Copy link
Contributor

Closing as a stale issue and that PowerShell Core is deprecated on desktop systems. We will be verifying that Plaster works properly in PowerShell 7.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants