I have done on the coding part in visual studio code while using command palette to download symbols i can't able to download it rather in output it displays about the authentication has failed. How to solve that one ?
Related
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?
I have visual studio code on linux . I want to use it as a code editor .and maybe debug it
(currently debug via gdb)
Downloaded a code of the (big) project from source control and compiled it from command line.
I don`t know how to open a project in visual studio code (it should also be configure to work with source control (git)).... can someone help
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.
I'm a new user of Visual Studio Code and I came across the following error (see below) when trying to launch a Terminal inside VS Code.
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe" terminated with exit code: 3221225477.
I've tried fixing this by following the instructions on [Visual Studio Code Troubleshoot Terminal] (https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch) and also going through the Get Started documentation on the Visual Studio Code website.
I've also tried copying the error message and pasting on Google to search for a solution but only one relevant site came up here and I still could not find a fix.
I'm using a Dell XPS machine running Windows 10 (x64) and Visual Studio Code 1.51.0 (x64 UserSetup).
Can someone please assist? Thanks in advance!
Try the following:
If your computer is running powershell, turn it off.
Control Panel -> Programs -> Turn Windows features on of off
Search Window Powershell 2.0 -> Uncheckbox -> OK
Restart
Almost every time I try to rebuild a C++ project in Visual Studio 2010 after having recently launched the build target from Visual Studio, I get this error.
LINK : fatal error LNK1104: cannot open file 'D:\Programming\Projects\SpecsLauncher\Release\SpecsLauncher.exe'
I have used ProcExp from Sysinternals to check and see which application still has the file open, but it comes up with the System process as still having it open.
It does not appear anywhere in the Windows Task Manager, and closing and re-opening Visual Studio makes no difference.
I can't even delete the build target from Windows Explorer.
I do not experience this issue with anything other than executables built and run from Visual Studio.
I thought it might be my anti-virus (Symantec Endpoint Protection), so I tried temporarily disabling it, but it made no difference.
The only thing I can do is wait about 4 minutes and then try again.