You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During Install-PSResource with -NoClobber produces an error for a command conflict when there is none.
Steps to reproduce.
Get-Command*acme*# returns nothingInstall-PSResource acme-ps -TrustRepository -NoClobber -Verbose
VERBOSE: Current user scope installation path: C:\Users\Thomas\Documents\WindowsPowerShell
VERBOSE: All users scope installation path: C:\Program Files\WindowsPowerShell
VERBOSE: Scope is: CurrentUser
Install-PSResource: Command(s) with name(s) 'System.Linq.Enumerable+WhereEnumerableIterator`1[System.Management.Automation.PSObject]' is already available on this system. Installing 'ACME-PS' may override the existing command. If you still want to install 'ACME-PS', remove the -NoClobber parameter.
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.91. Please mark this comment with 👍 or 👎 to give our bot feedback!
ThomasNieto
changed the title
Install-PSResource does not honor DefaultCommandPrefix during NoClobber
Install-PSResource with NoClobber produces command conflict when there is none
Jul 31, 2020
During
Install-PSResource
with-NoClobber
produces an error for a command conflict when there is none.Steps to reproduce.
The text was updated successfully, but these errors were encountered: