microsoft / microsoft/vscode-mssql

[Bug]: Ensure correct NuGet/DLL version is used when skipping download

Open
#21,412 0 comments 0 reactions 1 assignee View on GitHub

@ssreerama is already working on this.

Since Mar 2, 2026.

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

Description

### Description

Currently, if the required DLLs are already present, we skip the NuGet download. However, we do not verify whether the existing DLLs match the expected version.
This can lead to cases where an incorrect or stale DLL version is used.

Ensure the customer is always using the correct version of DLLs with the corresponding sql porj extension version

### Steps to Reproduce

1. internal work
2. Install the sql database projects extension in a offline proxy environment.
3. NuGet download will be bypassed if the dlls are present.
4. Ensure the dlls are latest version of that extension, if not hep customer with message and udpate the dlls.

### 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

. Any version helps to validate

### Confirmation

- [x] I have searched existing issues and couldn't find a match
- [ ] 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.