Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Oct 6, 2025

This PR migrates the solution to the new .slnx file format by running dotnet sln migrate as per the .NET 9 documentation. The legacy .sln file has been removed to avoid CI/CD ambiguity errors.

What Changed

  • Generated IntelliTect.TestTools.Console.slnx using dotnet sln migrate
  • Removed the legacy IntelliTect.TestTools.Console.sln file to prevent "more than one solution file" errors in CI/CD pipelines

About .slnx Format

The .slnx format is the new XML-based solution file format introduced in .NET 9 that offers several advantages:

  • More compact: The XML format is significantly smaller (438 bytes vs 2.1KB for this solution)
  • Human-readable: Cleaner XML structure compared to the MSBuild format
  • Better for version control: Easier to read diffs and resolve merge conflicts
  • Forward-compatible: Will be the standard format going forward in .NET

Verification

The solution builds and tests successfully with the new format:

dotnet restore
dotnet build --configuration Release
dotnet test --no-build --configuration Release

All projects (IntelliTect.TestTools.Console and IntelliTect.TestTools.Console.Tests) and solution items are preserved in the new format. All 32 tests pass successfully.

Original prompt

run dotnet sln migrate (https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-sln#migrate) to add in a .slnx file to live alongside our .sln file for now (.sln for backwards compatibility for now)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI and others added 2 commits October 6, 2025 17:52
Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
Copilot AI changed the title [WIP] run dotnet sln migrate (https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-sln#migrate) to add in a .slnx file to live alongside our .sln file for now (.sln for backwards compatibility for now) Add .slnx file using dotnet sln migrate Oct 6, 2025
@BenjaminMichaelis
Copy link
Member

@copilot maybe we can drop the .sln file and just keep the .slnx?

We get this otherwise.

Run dotnet restore
dotnet restore
shell: /usr/bin/pwsh -command ". '{0}'"
env:
DOTNET_ROOT: /usr/share/dotnet
MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.
Error: Process completed with exit code 1.

Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Oct 6, 2025

@copilot maybe we can drop the .sln file and just keep the .slnx?

We get this otherwise.
...

Removed the .sln file as suggested. Now only the .slnx file remains, which resolves the "more than one project or solution file" error in CI/CD. Verified that dotnet restore, dotnet build, and dotnet test all work correctly with just the .slnx file.

Copilot AI changed the title Add .slnx file using dotnet sln migrate Migrate to .slnx solution file format Oct 6, 2025
@BenjaminMichaelis BenjaminMichaelis marked this pull request as ready for review October 6, 2025 18:48
@BenjaminMichaelis BenjaminMichaelis merged commit d2b5822 into main Oct 6, 2025
4 checks passed
@BenjaminMichaelis BenjaminMichaelis deleted the copilot/fix-09cf6734-a1d8-4012-88d7-ed3e971a343d branch October 6, 2025 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants