Tooling status

[manuelelucchi]

A pretty common use case for Sql Projects would be being used alongside .NET services and the Aspire AppHost. This is fundamentally a pain at the moment, since

• If you use Visual Studio 2026, SqlProj SDK style are not supported (for some reason they are on VS 2022 Preview)
• If you use VSCode, the C# extension doesn't recognize the .sqlproj in the solution, while the MSSQL extension only sees the projects
• Of course SSMS only supports sql projects
• You need the .sqlproj to be in the solution to use them with aspire, therefore you have to deal with all the previous problems

The sad thing is that Rider, which is not from Microsoft, handles it all correctly

I think it would be good if the teams involved could cooperate more to improve these behaviours

[dzsquared]

Making sure I capture your explicit request correctly -

The sad thing is that Rider, which is not from Microsoft, handles it all correctly

Is it accurate that you'd prefer to have minimal SQL projects support directly alongside C# projects instead of multiple tools with more specialized functionality (or interfaces within the same tool as in VS Code)?

As you may have seen in https://aka.ms/sqlprojects-roadmap, I do strongly recommend folks voice their interest for VS on the DevComm feedback site as that is the most visible.

If you have a prefered singular environment, I'm curious what it is!

[ErikEJ]

For me, the preference would be VS 2026, even just support to have a basic Microsoft.Build.Sql project build with my C# projects (fine if it was without any tooling at all, actually)