IntelliSense included in Python's Microsoft Extension vs Visual Studio IntelliCode - visual-studio-code

IntelliSense Autocomplete
vs
Visual Studio IntelliCode
Should I avoid using Visual Studio IntelliCode when using default IntelliSense?
What's the difference between them? What are advantages/disadvantages?

I'm a software engineer on the IntelliCode team. IntelliCode is meant to augment the default IntelliSense experience and save you time by putting what you're most likely to use at the top of your completion list. IntelliCode recommendations are based on thousands of open source projects on GitHub.

Related

search analyzer and formatter for Visual studio code

I would like to find a linter to analyze the formatting of my code, and also use the linter locally to format my code. And I would want to be able to do that with Visual studio code (and ideally, also Visual studio).
Right now, I am using Visual studio with resharper. But it's way too slow for me.
So I installed visual studio code, installed the extension omnisharp and roslynator, to be able to have the same formatting rules as resharper. So it works well, I configured my config file to display error when a rule is not respected, like that :
My issue is, I can't find a way to fix all these issue with a shortcut, like I use to do with Visual studio and resharper.
The shortcut shift+alt+F does not fix all my errors, and the command omnisharp "fixall" act weirdly, it remove my function Hi..
Do you have suggestion of setup with visual studio code to be able to format the code directly (not via a command line, but from a shortcut), and as advanced as resharper, and that could also work as a linter to analyze the code on the CI?

Is it possible to run Visual Studio Code commands from Markdown?

Is it possible to run Visual Studio Code commands from Markdown? I noticed that, for example [cpptools](vscode:extension/ms-vscode.cpptools) shows the extension's page. I wondered if executing a command from the command palette would also work, and if it is something of an URI.
It proved difficult to track down the documentation but in fact this is possible, see: https://github.com/microsoft/vscode/issues/140733
Say your command is referenced as pkg.command, then this URL in Markdown can be clicked to execute it:
[Run It](command:pkg.command)
This works out of the box in modern VSCode.
Link processing using protocol vscode for example [cpptools](vscode:extension/ms-vscode.cpptools) is performed only by Visual Studio Code. For now, it handles links if they point to extensions, but does not support link to commands. But the Visual Studio Code development team can add this if they see fit for the developers.
But, in my opinion, this functionality is not necessary.

How to use VScode Keybindings in Visual studio 2019

I need to use Visual studio 2019 for my school, I love the VSCode shortcuts (for Example ALT+SHIFT+Down - duplicates a line) but I can't seem to figure out how to use them in Visual studio 2019.
I already tried the answer provided: here , didn't work.
I tried to copy the JSON keybindings file from VSCode but Visual Studio 2019 keybindings doesn't seem to work that way.
Any ideas?
Thanks

Is it possible to add auto-completion into external code editors for Unity

I just started using Unity with Visual Studio Code and got it up and running to use it instead of the default code editor but VSC doesnt display auto-completion and I am wondering if it is even possible to add this feature into Visual Studio Code and if yes, how to do so.

Visual Studio Code - IntelliSense missing for static methods

I've installed Visual Studio Code 0.10.8 with ms-vscode.PowerShell-0.4.1 extension.
IntelliSense ([ctrl]+[space]) is working fine:
... but not for static methods:
There are no such problems in PowerShell ISE:
I really like the feel and speed of vscode, but I'm working with lots of .NET classes and won't switch from ISE without full IntelliSense support. Any ideas on how to fix this?
There is no built in official PowerShell support for Visual Studio Code.
You may have either found a bug, or a missing featuring of the PowerShell extension.
I'd recommend posting an issue on their GitHub repo: https://github.com/PowerShell/vscode-powershell