microsoft / microsoft/vs-solutionpersistence
SSMS and Visual Studio both claim .slnx, causing SQL solutions to open in Visual Studio
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 213
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I have both Visual Studio and SSMS installed.
When I click a .slnx file:
- If it is a .NET / Visual Studio project, I want it to open in Visual Studio.
- If it is a SQL script / SSMS project, I want it to open in SSMS.
Right now Visual Studio can take over the .slnx file association, so SQL script projects open in Visual Studio instead of SSMS.
Is there a supported way for .slnx to say which app should open it?
For example, could .slnx include a simple setting or type marker so Windows, Visual Studio, or SSMS can tell whether it is a .NET solution or an SSMS SQL script solution?
Current workaround is to manually choose the app or use a custom launcher, but it would be better if this worked automatically.
Contributor guide
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
Review the repository's serializers and models for .slnx files, then compare the current format with how Windows, Visual Studio, and SSMS choose file associations. A complete change would need a defined, supported marker and documented behavior that selects the appropriate application; the issue does not name a file or test to start from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100