Closed Liturgist closed 1 year ago
Whilst this is an issue with a cmdlet in a module that is shipped with PowerShell - this is caused by an externally developed module in PackageManagement
which is not maintained or developed in this repo and is no longer getting active development as per the readme in it's repo
You may be able to replace use of Install-Package from PackageManagement
with commands from PSResourceGet
instead, which is currently undergoing active development and is the future replacement for both PackageManagement
and PowerShellGet
@kilasuit, PowerShellGet
does not have an Install-Package
command.
Where can I find detailed information regarding the similarities and differences between a 'module', 'script', and 'package'?
Prerequisites
Steps to reproduce
Expected behavior
Actual behavior
Error details
Environment data
Visuals
No response