microsoft / microsoft/vscode-dotnettools
NuGet add package is way too slow
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Type: Bug
The experience to add a NuGet package via command is way too slow. Like 30s for a search.
https://github.com/user-attachments/assets/2332be69-a58d-4b63-a41d-b42a7d6c5475
Extension version: 1.50.20
VS Code version: Code - Insiders 1.104.0-insider (d2edee24762a3923e2422d3f61528ae4b1381a33, 2025-08-20T06:50:12.030Z)
OS version: Windows_NT x64 10.0.26120
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 9 3900X 12-Core Processor (24 x 3793) |
| GPU Status | 2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 127.92GB (82.66GB free) |
| Process Argv | --log timheuer.nupkg-viewer=trace --log timheuer.trxview=trace --crash-reporter-id 961e68ed-cec6-437f-8e5f-e44a8abbf88f |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
pythonvspyt551:31249597
nes-control:31370901
nativeloc1:31118317
dwcopilot:31158714
dwoutputs:31242946
copilot_t_ci:31333650
g012b348:31231168
pythoneinst12:31251391
6gi0g917:31259950
996jf627:31264550
pythonrdcb7:31268811
usemplatestapi:31297334
747dc170:31275146
pythonpcpt1cf:31345881
6518g693:31302842
9d2cg352:31346308
j97ad248:31349650
0g1h6703:31329154
nes-emitfast-1:31333560
6abeh943:31336334
envsactivate1:31349248
0927b901:31340060
nb18600_tf:31359574
1je7-usegpt41:31345955
editstats-enabled:31346256
gendocstringt:31358906
asdad:31365766
pylancealldocst:31362265
gemagent1cf:31368470
cloudbuttont:31366566
todos-1:31366868
v2-prompt:31370220
search_len1:31370369
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the NuGet add-package search using the reported extension, VS Code, and Windows versions, and inspect trace logging for the command. The issue names no files or tests, so first identify the package-search entry point and isolate the source of the roughly 30-second delay. Done means package search completes promptly and the behavior is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100