The process of installing, configuring, and customizing Visual Studio to support development workflows across languages, platforms, and workloads.
Thanks for reaching out. From the information shared, the behavior you are experiencing is expected when working with newer versions of Microsoft Visual Studio 2026 together with the Unity Editor.
Strating with newer Visual Studio releases, the IDE may generate .slnx solution files. However, when a project is managed by Unity, the solution and project files are generated and controlled by Unity itself, not by Visual Studio. Because of this, the Visual Studio setting under Tools-> Options-> Projects and Solutions-> General -> Default Solution File Format does not override Unity's generation process.
Why .slnx is still generated
When you open Unity Project in Visual Studio:
- Unity regenerates the solution files whenever scripts are refreshed or the project is opened.
- Unity determines the solution format it generates.
- Visual Studio simply opens whatever solution Unity provides.
Therefore, even if Visual Studio is configured to prefer .sln, Unity may still recreate the solution using its own configuration.
Recommended Workaround
Please try the following steps to ensure Unity generates the traditional .sln files:
- Open your project in Unity Hub.
- In Unity Editor, navigate to: Edit -> Preferences -> External Tools.
- Ender External Script Editor, select: Visual Studio
- Enable the options:
- Generate all .csproj files
- Regenerate project files
- Click Regenerate project files. After That:
- Close Visual Studio.
- Delete the following files from your Unity project root:
- .slnx
- .csproj
- Reopen the project from Unity by double-clicking a script. Unity should regenerate the .sln solution file compatible with Visual Studio.
Additional Notes
if .slnx continues to be generated, it may indicate that the Unity version you are using has begun supporting the newer solution format. In that case, the behavior is controlled by Unity's integration package rather than Visual Studio.
You may also consider:
- Updating the Visual Studio Tools for Unity component inside the Visual Studio Installer.
- Updating Unity to the latest LTS patch where .sln compatibility improvements may be included.
Please let us know if you require any further assistance we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer".