microsoft / microsoft/vscode-mssql

[Bug]: Sql Projects - Visit all path resolutions and confirm they are cross-plat support

Open
#21,197 1 comment 0 reactions 1 assignee View on GitHub

@ssreerama is already working on this.

Since Feb 13, 2026.

Bug Team-filed (internal) User-filed
Dominant language
TypeScript
Stars
1.9k
Forks
610
Avg merge
2d 3h
Merged PRs (30d)
97

Description

### Description

In several places, SQL projects use path.join without normalizing relative paths to a cross‑platform format, which can cause path comparison failures and lead to unexpected issues.

### Steps to Reproduce

no repro, just find out all usages and verify they are good or need fixes

### Affected Area

- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [ ] Query results panel
- [ ] Object Explorer
- [ ] GitHub Copilot integration
- [ ] Preview/Edit data
- [ ] Table Designer
- [ ] Schema Designer
- [ ] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [ ] DACPAC/BACPAC export/import
- [x] SQL Database projects
- [ ] Query Plan Visualizer
- [ ] Other (please describe below)

### If you selected "Other", please describe the affected area

_No response_

### Environment Information

main local

### Confirmation

- [x] I have searched existing issues and couldn't find a match
- [x] I want to work on this issue

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.