You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 3 of the xUnit migration docs states "You should see TUXU0001 warnings in your build output for xUnit code that can be converted.". But TUXU0001 is information level and won't be in the output of dotnet build, so this step leads to confusion that the analyzer isn't working, even though it is working.
Proposed Solution
Remove this step and skip straight to applying changes, or explain that the analyzer outputs can be viewed without being applied with dotnet format analyzers --severity info --diagnostics TUXU0001 --verify-no-changes
Alternatives Considered
No response
Feature Category
Documentation
How important is this feature to you?
Nice to have - would improve my experience
Additional Context
No response
Contribution
I'm willing to submit a pull request for this feature
Yes, they took care of the bulk of the work. There was some edge cases that produced unexpected results - I'll log separate issues for those. Thank you for building out the migration tooling, it made things much simpler!
Activity
thomhurst commentedon Feb 14, 2026
Thanks for the feedback.
Did the migrators work well for you out of interest?
ascott18 commentedon Feb 14, 2026
Yes, they took care of the bulk of the work. There was some edge cases that produced unexpected results - I'll log separate issues for those. Thank you for building out the migration tooling, it made things much simpler!