microsoft / microsoft/vscode-dotnettools
[SUGGESTION] Generate `.slnx` in workspace without solution file when `dotnet.preview.enableSupportForSlnx` is `true`
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Describe the feature you'd like
Today, when a workspace contains C# projects, but no solution file (neither .sln nor .slnx), a .sln file is generated for the user automatically.
With dotnet.preview.enableSupportForSlnx set to true, the extension should generate a .slnx file instead.
Alternatives considered
The extension could prompt the user for which solution format they want created.
Environment Information
- VSCode: 1.100.0
- C# DevKit: 1.19.60
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the workspace path that currently generates a .sln when C# projects have neither a .sln nor a .slnx, then inspect how dotnet.preview.enableSupportForSlnx is read. Done means a workspace without either solution file generates a .slnx when the setting is true, while existing behavior remains unchanged otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100