VS Code On Linux
-
The whole point of this exercise is to get away from Windows completely. If I have to use Visual Studio to create the project, I may as well stay with Windows. And ya know, it's gonna take a crapload of effort to convince me that a commandline interface is better/easier than a GUI.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013It does seem like a tremendous regression. I think many like it simply because it is cryptic: kind of a throwback to the "super sleuth decoder ring." I'm too old to try to be cool; I liked command line back in my UNIX administrator days, but that was a different lifetime. Remembering how to do mundane crap is what a computer is for, and I am tired.
-
It does seem like a tremendous regression. I think many like it simply because it is cryptic: kind of a throwback to the "super sleuth decoder ring." I'm too old to try to be cool; I liked command line back in my UNIX administrator days, but that was a different lifetime. Remembering how to do mundane crap is what a computer is for, and I am tired.
Werd
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
When you install VS Code on Linux, does it also install the .Net Core stuff (core and sdk)?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013VS Code is a standalone editor; it doesn't install .NET, it is not based on .NET. It's actually based on Electron[^], and was originally written as a competitor to Atom[^], which of course was written and released by the team at Github. As you know, Microsoft acquired Github fairly recently - so now (more or less) they are supporting two different Electron-based cross-platform editors (Atom and VS Code). One or the other is likely to die or be merged into the other; my bet is on VS Code being the "winner". VS Code as an editor - just like Atom - can be expanded upon using plug-ins and extensions. But right out of the box, it is geared toward code editing; it has "built-in" support for Git, for instance. But all of this can be extended and expanded to make the editor into virtually a full-fledged IDE. Most of the plug-ins, etc are similar to (or even the same) as the ones available for Atom - though there are a few out there that don't cross eco-systems. Even so, you can usually find one that'll work similar to the other, so if you have a favorite plug-in on Atom, switching to VS Code isn't too much of a headache. So if both editors are so similar - why switch, or why use one over the other? Well - that's only a decision you can make for yourself, but there is one area where (I have found) VS Code shines over Atom: Time to startup. VS Code is simply the fastest. I am not sure why. Basically, if I am editing a text file, I want it up as quickly as possible after clicking on the file to open it. With Atom, I was looking at several seconds; I never timed it, but it felt like an eternity. Once loaded, though, I never experienced any other issues, and opening further files was fast. It was just that initial startup. With VS Code, though - you click on your file, and it is up almost instantly; maybe a 1-2 second lag at most. But that's a really niche use-case; if you have the editor start up when you log in to your system, right off the bat, then it kinda negates the issue. I'm not always editing a file though, and so I don't have anything auto-start (at least at home - at work it's a different story). As far as .NET development - if you need or want a cross-platform dev environment geared to that, then grab a copy of MonoDevelop[
-
John Simmons / outlaw programmer wrote:
I started it up and don't see a way to create a new project.
VS Code is totally non-intuitive IMO. But I guess that really only means I haven't worked with it enough to learn How It Does Things. Anyways, to your point, I think you just create a folder and start putting code files into the folder. The folder is the "project." I may be wrong.
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Marc Clifton wrote:
S Code is totally non-intuitive IMO.
It just takes a bit of time to reveal it's awesomeness. Also it does feel "non-intuitive", if we are a bit so used to Visual Studio user experience. VS Code feels such a perfect one for non-MS stack. Been using it to review some LAMP code. It's doing truly well. This is such a badly needed one for the wild-n-free world. Where Notepad++ has been ruling it for all these years. It's de-throned now. lol
Full Reset
-
It does seem like a tremendous regression. I think many like it simply because it is cryptic: kind of a throwback to the "super sleuth decoder ring." I'm too old to try to be cool; I liked command line back in my UNIX administrator days, but that was a different lifetime. Remembering how to do mundane crap is what a computer is for, and I am tired.
It's nice to see some senior devs actually valuing their time. Having had to deal with command-line stuff recently, it made my blood boil. Everytime a path is involved, that's 10 minutes of trial and error and debugging. Googling is usually no help because Linux people already assume you only use ASCI character paths with no UTF and absolutely no spaces. And you have to revert your slashes from Windows. But not all of them. Oh, and learn escape char combinations so you can put a letter in an argument. Do I use " here or ' ? Do I need -c or --c ? Oh god, I need to pass 2 sub-parameters here, how do I do that... comma separated ok, but my parameters has a comma... What, you though computers where tools to helps us? No, YOU must bend to your computer. I could go on and on. This is the definition of a terrible experience, the terminal is not made for humans and there's no motivation to improve beyond the Unix model of the 60's.
-
VS Code is a standalone editor; it doesn't install .NET, it is not based on .NET. It's actually based on Electron[^], and was originally written as a competitor to Atom[^], which of course was written and released by the team at Github. As you know, Microsoft acquired Github fairly recently - so now (more or less) they are supporting two different Electron-based cross-platform editors (Atom and VS Code). One or the other is likely to die or be merged into the other; my bet is on VS Code being the "winner". VS Code as an editor - just like Atom - can be expanded upon using plug-ins and extensions. But right out of the box, it is geared toward code editing; it has "built-in" support for Git, for instance. But all of this can be extended and expanded to make the editor into virtually a full-fledged IDE. Most of the plug-ins, etc are similar to (or even the same) as the ones available for Atom - though there are a few out there that don't cross eco-systems. Even so, you can usually find one that'll work similar to the other, so if you have a favorite plug-in on Atom, switching to VS Code isn't too much of a headache. So if both editors are so similar - why switch, or why use one over the other? Well - that's only a decision you can make for yourself, but there is one area where (I have found) VS Code shines over Atom: Time to startup. VS Code is simply the fastest. I am not sure why. Basically, if I am editing a text file, I want it up as quickly as possible after clicking on the file to open it. With Atom, I was looking at several seconds; I never timed it, but it felt like an eternity. Once loaded, though, I never experienced any other issues, and opening further files was fast. It was just that initial startup. With VS Code, though - you click on your file, and it is up almost instantly; maybe a 1-2 second lag at most. But that's a really niche use-case; if you have the editor start up when you log in to your system, right off the bat, then it kinda negates the issue. I'm not always editing a file though, and so I don't have anything auto-start (at least at home - at work it's a different story). As far as .NET development - if you need or want a cross-platform dev environment geared to that, then grab a copy of MonoDevelop[
Also, VSCode (for whatever reason) doesn't support text highlighting or intellisense for C# or C++ out of the box. You have to go get plugins for that. I'm using Microsoft's plugins and they work really well. On the plus side, there are plugins for just about any language in common use. I have SQL, Swift, C#, C++, etc. installed. Also found a very good diff plugin. You might want to take a look at this: Using .NET Core in Visual Studio Code[^] as a good starting point for both. With the dotnet new command, I always use the --output option because it creates the folder and then creates the new project in that folder. The documentation is here[^] I've enjoyed using VSCode and .Net Core together on a Mac. It's getting better with each release (so far). alan
-
When you install VS Code on Linux, does it also install the .Net Core stuff (core and sdk)?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Wow, why so much VS Code hate (looking at many of the previous reply trees)? First, yes, it's an IDE. It supports project management, editing, syntax sense, debugging and source control. Is there something else an IDE is supposed to do? Second, it's lightweight. You add plugins for what you want to do. It doesn't download everything when you install it: you add the bits you want. It *does* suggest bits you might like. The command window is pretty simple and comes with lots of help. To get started, you *don't* have to start a project in Windows. That poster was making a helpful suggestion to accelerate familiarity. To get started, download it, create a folder, open the folder with VS Code, and start adding files. It's pretty simple. I have to laugh at the people recommending Eclipse instead. Sorry, folks. Eclipse works, but it's a classic poorly managed open source project. It's a ball of sticky stuff with bits slapped on all over the place. I use it every week, have done for 10 years (most embedded systems use it as a base, because it's free), and shudder every time I open it. I think the team motto is "we're programmers, we don't need no stinkin' usability!".
