Reenable CheckTargetFrameworkDisplayName test #48471
Open
Conversation
This file contains 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
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
|
Would an alternative fix here be to keep run but use the /tl:off flag? @baronfel any changes coming that auto-detect this or change the default for run? |
|
Can try using /tl:off, but considering the issue PR mentioned that |
This reverts commit ac6f46a.
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.
Fixed #45148
When using the
dotnet runcommand to execute the project, the standard output is processed byStripTerminalLoggerProgressIndicators. This step can clean up progress indicators from the output but might also affect the format and content of the output. By using thedotnet execcommand to directly execute the builtDLL, the standard output is compared directly to the expected framework display name.