F5 is the default but you can set your own keyboard shortcuts from the File->Preferences->Keyboard Shortcuts menu
There appears to be no way to bind a keyboard shortcut for running an arbitrary task. https://github.com/Microsoft/vscode/issues/6550 By default F5 is "continue debugging," but debugging is limited to Node, so I don't think that's what I want. Incidentally my MBP has no F5 key :)
There are debugging extensions for environments beyond Node.
Also, Ctrl+Shift+B is the default shortcut for whatever arbitrary task you have set as your Build Task in .vscode/tasks.json.
I'm used to being able to run my program via command-R or some other key equivalent. I haven't been able to find a way to do this conveniently from VSCode. How do other VSCode users run their programs?
The Tasks system in VSCode is quite powerful: https://code.visualstudio.com/Docs/editor/tasks Also, the integrated Terminal (Ctrl+`) is more useful with each version.
How do you (personally) use tasks? Do you bind a key to the "Run Task" command and then type the task name in? Doesn't that feel inefficient?
I'm just trying to get the edit/build/run cycle down. So far the "run" part is missing for me.
This is an off topic, but I just learned from the article that PowerShell will soon be the default in place of cmd.exe in Windows 10. I welcome this change as I found the experience of using PS was superior to that of bash/zsh in general cases. But I hope they figured out the performance problem. As of writing, in the stable version of Windows 10, PS is perceptually slower than cmd, so I was forced to use PS only whe…
Yeah this is the one thing with PowerShell: with great power comes, erm, not so great performance. I've never been a full-time shell user so after years of occasionally getting some stuff automated using bash discovering Powershell really was like a breath of fresh air.. No more trying/failing to come up with the correct regex to parse the plain text spit out by tools. Command-line completion of arguments. A whole bunch of sane defaults and command names making things easy to discover. Etc. Now at first I only ran PS on a beefy workstation and didn't notice it was kinda slow (even for common operations). But on not-so-beefy machines: yeah, not nice. Then again, cmd is worthless in comparsion with PS so I stopped caring. Thing is also: the time gained by how fast I can get stuff done in PS probably makes up for the time lost trying to figure out the weird syntax of other shells, especially cmd.
VS Code is a web dev IDE. Microsoft has lost the mobile platform wars and pushing the web is a way of countering that. Plus, web and azure do go hand-in-hand, as you point out.
They lost the mobile phone, but I bet they will win the hybrid tablet/netbooks one, given how Android tablets disappeared from many consumer shops here in Germany, only to be replaced by Windows 10 ones. Samsung and Asus ones seem to have been the surviving brands and even they have Win10 devices on their brand sections.
No they won't. No one wants to use clunky non touch optimized windows desktop apps on a tablet. Besides, UWP was a failure.
I would like to try it for native development. How do you run and debug your C++ programs from VSCode?
https://code.visualstudio.com/docs/languages/cpp > VS Code supports tasks that you can configure to build your application, and natively understands the output of MSBuild, CSC, and XBuild.
Yes, building works well. But how do you run your application?
(To be clear I'm asking what workflow users use personally, since it seems like nobody else has this issue.)
I would rather have devs invest time in serious functionality then doing stuff like GUI. Otherwise, this quickly turns to nonsence such as Nano server image builder [1] because Microsoft is still babysitting people who CBB to spend few hours to learn Powershell basics and need a GUI that generate 1 liner script. Microsoft should definitelly rise beyond click next culture. [1] https://blogs.technet.microsoft.com/nanos…
Discoverability and ease of use ARE serious functionality.
There are different ways to discover stuff. Powershell itself clearly proves that it can be done on system level without any GUI whatsoever.
We had the "ease of use" in GUI paradigm for decades and it didn't hold. Why don't you give it a chance as a text ?
It's probably a complex set of factors including developer good will and competition in the marketplace (VSCode is obviously directly competing with Atom, for instance, which is also free). One interest small piece of the larger puzzle is that the Monaco text editor at the heart of VSCode was originally built for Azure and Visual Studio Team Services cloud editing. It was then also subsequently embedded into IE's Dev…
VSCode vs Atom (in my opinion) isn't even a contest. Maybe Atom is super nice for some web dev stuff, but as a full flown IDE I just don't see the features.
Are you confusing VSCode with Visual Studio? VSCode is not an IDE, it's an editor, much like Atom.