Remove sentence about 'extra configuration file' next to the single-file app #43042
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
…efers to non-runtime configuration
elinor-fung
commented
Oct 14, 2024
gewarren
approved these changes
Oct 14, 2024
elinor-fung
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
As is, the sentence can be read as stating that extra runtime configuration files (for example, a second *.runtimeconfig.json) can be placed next to the single-file app and be respected at runtime - dotnet/runtime#108814. This is not the case - when a single-file app finds the runtime configuration files embedded in itself, it will not look next to it for loose runtime configuration files.
cc @agocke @VSadov
Internal previews