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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Respect AppContext.SetData with APP_CONFIG_FILE key #56748
Respect AppContext.SetData with APP_CONFIG_FILE key #56748
Changes from all commits
2d3d474
0a02303
cdbceb1
afcf7a5
79fe28e
eec3437
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is implicitly prefixing with whatever the current directory is at the time the config system is initialized, I guess?
In the desktop code it is using the appbase to prefix (naming.cpp line 3241 .. assuming I'm looking in the right place)
I think in .NET Core that is AppDomain.BaseDirectory, so should this be
Path.Combine(AppDomain.CurrentDomain.BaseDirectory, externalConfigPath)
? There is something similar higher up.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can change the tests to set Environment.CurrentDirectory to something random before reading the value (I'm guessing the test will fail right now)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you use
Path.Combine
you need to be careful with paths that begin with\
, as you'll get the second path against the root of the current directory. Trim the start of theexternalConfigPath
for safety.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have used
Path.GetFullPath(externalConfigPath, AppDomain.CurrentDomain.BaseDirectory)
which seems to be working fine. The tests are now changing CurrentDirectory to validate we are relative to the BaseDirectory and not CurrentDirectoryThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm seems that overload is not available everywhere...