[release/9.0] Add .slnx fallback for TestHost content root discovery#64953
Merged
wtgodbe merged 2 commits intorelease/9.0from Jan 13, 2026
Merged
Conversation
Co-authored-by: halter73 <54385+halter73@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update WebHostBuilderExtensions to avoid exception with .slnx file
Add .slnx fallback for TestHost content root discovery
Jan 6, 2026
halter73
approved these changes
Jan 8, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request adds non-breaking .slnx fallback support to the UseSolutionRelativeContentRoot method in TestHost. When searching for solution files with the "*.sln" pattern, the method now falls back to searching for .slnx files if no .sln file is found, preventing the InvalidOperationException that would previously occur.
Key changes:
- Added .slnx fallback logic that only activates when no .sln file is found and the search pattern is "*.sln"
- Maintained .sln precedence to avoid breaking changes where .slnx files could shadow .sln files in parent directories
- Added comprehensive tests validating both the fallback behavior and .sln precedence
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/Hosting/TestHost/src/WebHostBuilderExtensions.cs | Added conditional .slnx fallback logic after .sln search fails, maintaining backward compatibility |
| src/Hosting/TestHost/test/WebHostBuilderExtensionsTests.cs | New test file with two tests: one verifying .slnx fallback and one verifying .sln takes precedence over .slnx |
Member
|
/backport to release/8.0 |
Contributor
|
Started backporting to |
10 tasks
halter73
approved these changes
Jan 9, 2026
BrennanConroy
approved these changes
Jan 10, 2026
This was referenced Feb 16, 2026
Merged
Merged
Open
Merged
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
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.
Add .slnx fallback for TestHost content root discovery
Description
This pull request adds
.slnxfallback support to the test-onlyUseSolutionRelativeContentRootmethod in theMicrosoft.AspNetCore.TestHost. When searching for solution files with the*.slnpattern, the method now falls back to searching for.slnxfiles if no.slnfile is found, preventing theInvalidOperationExceptionthat would previously occur before test developers can easily callUseSolutionRelativeContentRootthemselves.This has already been fixed in .NET 10 by #61305, but that included public API changes, so this is not a direct backport. Unlike, the .NET 10 change that treats
.slnxand.slnequivalently by default, this change will only fall back to looking for an*.slnxfile if the test server would otherwise throw anInvalidOperationExceptiondue to not being able to find an ".sln" file.Fixes #61304 in .NET 9.
Customer Impact
#61304 has gotten a lot of attention, because it is a pain point for migrating solution from
.slnto.slnx.Test projects that worked fine with an
.sln-based solution throw after migrating to*.slnxbefore developers even get access to theIWebHostBuilder, so they don't get the opportunity to easily manually reconfigure the content root by callingUseSolutionRelativeContentRootwith "*.slnx". Instead, the current general workaround is fragile and unintuitive:#61304 (comment)
Regression?
Not technically, but you could consider it a regression in behavior when migrating from
.slnto.slnxsolutions.Risk
This change only has an impact if starting the test server would otherwise throw an
InvalidOperationExceptionearly during initialization due to not being able to find an ".sln" file.Verification
Packaging changes reviewed?
.slnxfallback for content root lookup.Description
Problem:
UseSolutionRelativeContentRootthrew when only a.slnxexisted, and.slnxcould shadow.slnin parents.Changes:
.slnprecedence; if none found, retry search for.slnxwithout changing API..slnpreference and.slnxfallback discovery.Example:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.