Expand environment variables in input paths #484
Merged
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
mdanish-kh
requested review from
a team,
ryfu-msft and
yao-msft
and removed request for
a team
microsoft-github-policy-service
bot
added
the
Issue-Feature
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ryfu-msft
approved these changes
Nov 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Path.GetFullPath()will convert any slashes toPath.DirectorySeparatorCharwhich is backslash in Windows. This is done to make sure that when user gives a commandwingetcreate update xyz --out %USERPROFILE%/Desktop, then the output path on the CLI is printed with consistent slashes asotherwise it will be printed as
%USERPROFILE%/Desktop\manifests\xyz\versionMicrosoft Reviewers: Open in CodeFlow