-
Notifications
You must be signed in to change notification settings - Fork 138
Install-Module fails from ADO feed on Powershell 7 #686
Comments
@tgrader thanks for reaching out! I noticed that you are using Also, are the packages |
Hello, Please find the results you've requested below.
The problem is in Install-PackageUtility.ps1. This function calls a module-internal command named "Test-ValidModuleManifest" which triggers this error to be returned and does not honor the -Force parameter.
|
@travisgr PowerShellGet was originally really only meant to interact with PowerShell modules/scripts (hence why it's expecting to find a .psd1). We're working on a rewrite of PowerShellGet that better abstracts modules so that users have a better experience with generic .nupkgs and not just specifically PowerShell packages. Could you try using the latest prerelease version and if there's anything you'd like to see improved or any new features you think would be nice to have we can address those changes there. |
The latest version also fails to install this package. It's checking for the existence of a .ps1.
|
@travisgr thanks for trying this scenario out with PSGet V3. We're working to add better nupkg integration for packages like these which have neither .psd1 nor .ps1 file. These files are always present with PowerShell resources (off powershellgallery site) but we understand that packages from other repositories may not have this and we want to support those packages. The issue to track this work is here: https://github.com/PowerShell/PowerShellGet/issues/310 |
Prerequisites
Steps to reproduce
Expected behavior
Actual behavior
Error details
Environment data
Version
2.2.5
Visuals
No response
The text was updated successfully, but these errors were encountered: