PowerShell / PowerShell/vscode-powershell
.net intellisense break in workspaces
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Issue Type: Bug
This happens whenever I have anything loaded in Powershell with more than a few files.
Whenever I start VsCode and / or kill my session, there is a moment where the .net intelisense work normally.
However, a mere second after, anything from the .net space disappear and I only get the Powershell intellisense instead.
If using VsCode with a single file, it works fine.
As soon as I open a folder containing dozens of Powershell files (within or without a workspace), it work briefly as the session load, then break.
To reproduce:
- Clone https://github.com/itfranck/DudDashboard
- Start VSCode
- Open a ps1 file
- Type [System. then press space
For a few seconds, Collections / Threading / Net and other .Net namespace will be available.
If you repeat the operation a few time, the .Net namespaces stop being suggested and only Powershell suggestions occurs.
This happened for a few months with both Powershell and Powershell Preview extension and with both VsCode and VsCode insiders.
Here are the logs :
logs.zip
Context :
- I opened vscode
- I loaded my workspace containing my project
- I typed [system. then pressed CTRL + Space to force intellisense then I saw .net elements shown there and pressed Escape to close the intellisense.
- Powershell integrated console message showed in the terminal
- I pressed CTRL + Space again
- Intellisense showed again, but this time, all .net related suggestion had disappeared.
If there's any addtional logs I can include to provide more insight, I will be happy to.
Extension version: 2019.5.0
VS Code version: Code 1.37.1 (f06011ac164ae4dc8e753a3fe7f9549844d15e35, 2019-08-15T16:17:55.855Z)
OS version: Windows_NT x64 10.0.17763
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (8 x 3500) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_deferred_display_list: disabled_off skia_renderer: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.89GB (18.23GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Contributor guide
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
Reproduce the failure in a VS Code workspace using the DudDashboard repository, comparing a single PowerShell file with a folder containing many files. Start by reviewing the attached logs and the extension behavior around repeated IntelliSense requests. Done means .NET namespace suggestions remain available after the PowerShell session loads and after IntelliSense is reopened.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100