I prefer vscode simply because VS is excruciatingly slow. e.g. the file open pane in vscode pretty much instantly lists the file I'm looking for, while the counterpart in VS (ctrl+,) takes several seconds and intermixes search results for files and file contents, when I'm only interested in files.
DPack (free) has a useable file browser. I use Visual Assist (commercial) these days and that has one too. Both pop up pretty much instantly.
Both available from the extension marketplace.
> VS (ctrl+,) takes several seconds and intermixes search results for files and file contents, when I'm only interested in files.
I hate this a lot. It's gotten so bad the last couple of releases to the point that I try and use VS Code more in lieue of VS except debugging.
How they could let such fundamental functionality get broken is beyond me.
Ctrl+, followed by f filename, you will get the file.
The only reasons I use VSCode are the plugins I cannot get on VS, like Powershell, Rust, Azure tooling, and for stuff like Next.js, better use an editor that is anyway a browser in disguise.
Performance has never been a part of my decision flowchart.
I know it gets you the file...after several seconds. Vscode gives it instantly. I use this feature so often, it's basically a dealbreaker for VS.
I keep both editors open, but VS is basically just there to hit the compile button and for the occasional debugging.
Dunno, time to check your plugins slowing down the IDE.
Better not having Resharper around.
I have zero plugins installed. VS is just so slow that it's even outmatched by a javascript/Electron app like vscode.
Then it is definitely a "my computer/your computer" problem.
My computer has a PCIe 5 SSD, Ryzen 7950 and 128GB Ram. This is solely a VS problem, as you can see from the other posters with the same issue. And from the fact that vscode displays results instantly. It's only ever VS that's slow, accross any system I've ever used it with.