This repository was archived by the owner on Feb 12, 2025. It is now read-only.
Powershell -file doesn't handle arguments that are string[] #260
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
However executing the string like
-Commanddoes, basically if you do:powershell -file MyScript.ps1 -computers server1,server2,server3then the script recieves one argument calledcomputerswith the valueserver1,server2,server3however using
powershell -Command MyScript.ps1 -computers server1,server2,server3then the script receives one argument calledcomputerswith the value of an array containingserver1server2andserver3However I want this backwards compatible just incase unlike #255