Skip to content

SSMS and Visual Studio both claim .slnx, causing SQL solutions to open in Visual Studio #152

Description

@nd-wrk-1

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions