Remove razor_tooling from format example ci test #51563
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
As discussed in dotnet#51376, dotnet format launches another process for doing MSBuild invocations; the issue is we're trying to talk on the named pipe to that process and it just ... never connects. This appears to be an issue thats consistent across main and 10.0.1xx at the very least and only in razor_tooling. It might be due to some workspace configuration for razor. The dotnet-format team is working on a PR, but for now to unblock we will do this.
JoeRobich
approved these changes
Nov 4, 2025
Member
Author
|
/backport to release/10.0.1xx |
Contributor
|
Started backporting to |
Member
Author
|
/backport to release/10.0.2xx |
Contributor
|
Started backporting to |
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.
As discussed in #51376, dotnet format launches another process for doing MSBuild invocations; the issue is we're trying to talk on the named pipe to that process and it just ... never connects. This appears to be an issue thats consistent across main and 10.0.1xx at the very least and only in razor_tooling.
It might be due to some workspace configuration for razor. The dotnet-format team is working on a PR, but for now to unblock we will do this.