I can't recognise this new Microsoft. It's basically as if this was a new company wrt. Open Source and competing.
They now want to be Oracle in place of ORCL.
Visual Studio for Mac
121–130 of 435 posts
Re: Visual Studio for Mac
#122Earlier quoted context omitted.
You do know the difference between a text editor and an IDE? That's the difference between VS Code and VS.
Do YOU know the difference? Would it hurt to be more concrete? I'm going to venture a guess based on my assumptions, which are probably wrong, but then we can at least start a discussion: -VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another -VS Code doesn't support runtime debugging (breakpoints) -VS Code doesn't have a visual editor -VS Code doesn't ha…
VS Code supports GIT integration
Re: Visual Studio for Mac
#123Visual Studio for python is really great. Any hints the Python tools will be ported/compatible with the Mac version ?
I'm curious if you've tried Visual Studio Code for Python on Mac?
I've heard good things about it, and just this past weekend tried it out, but couldn't even get a simple Hello World working on it for Python.
I installed the common Python extension for it (Don Jayamanne's), but seems like it couldn't Link with the Python toolset. Ie, I could edit scripts with Python highlighting and autocomplete, but couldn't get them to execute. I gave up after an hour of trying and went back to pycharm.
I'd be interested in giving it another go, but worried if I'm needing to bang my head just for a Hello World, how bad it might get later on.
Re: Visual Studio for Mac
#124Earlier quoted context omitted.
> WRONG. The removal of a dozen keys from an already gimped keyboard is decidedly anti-developer. I am a developer and I could not care less about function keys. Why the duck would developers need function keys? Even for Vim, the age-old advice is to remap Esc so that you keep your hands on the home row. A flexible multi-touch strip of context-aware keys can do much more things -- e.g. map debugger step moves when I'…
If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.
I would presume that if the application hasn't been updated for the Touchbar, the Touchbar would default to displaying ESC F1 F2 F3 F4 etc..
Re: Visual Studio for Mac
#125Earlier quoted context omitted.
It's a toy for learning, nothing more.
It could be an MVP.
It is, for learning basic Swift. For developing you want to use a setup that allows you to handle thousands if not hundreds of thousands of lines of code. A single-process touch interface isn't that, I think.
Re: Visual Studio for Mac
#126> At its heart, Visual Studio for Mac is a macOS counterpart of the Windows version of Visual Studio. Does it have a monolithic install and update process that's essentially a slow, bloated black box? That's my main turn-off with Visual Studio on Windows, and even more so with Windows itself. As soon as Microsoft figures out efficient installation and updates via CLI without the need to reboot, they'll dominate the d…
A smaller and componentized install was a major focus for Visual Studio 2017. There's some more detail here: https://blogs.msdn.microsoft.com/visualstudio/2016/08/22/vis... Smallest install is 500MB .NET/C# install is ~3GB I also believe you won't have to reboot with most installs.
Nice, I totally wasn't aware of that. It's good to see VS finally headed down the right path in that regard.
Re: Visual Studio for Mac
#127Earlier quoted context omitted.
> WRONG. The removal of a dozen keys from an already gimped keyboard is decidedly anti-developer. I am a developer and I could not care less about function keys. Why the duck would developers need function keys? Even for Vim, the age-old advice is to remap Esc so that you keep your hands on the home row. A flexible multi-touch strip of context-aware keys can do much more things -- e.g. map debugger step moves when I'…
If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.
[deleted]
Re: Visual Studio for Mac
#128[deleted]
Re: Visual Studio for Mac
#129Earlier quoted context omitted.
Meanwhile, a "pro" user who's actually used the new Macbook Pro weighs in: http://www.huffingtonpost.co.uk/thomas-grove-carter/one-prof... Spoiler alert: he doesn't agree with the assessment of HN users who haven't actually used it.
That article is a typical example of "If it suits me, it must suit everybody." and your post is a good example for the no-true-Scotsman-fallacy of "Noone who _really_ used it dislikes it." All I really know about this is how I feel about it and I must admit that I am going to go back to the PC world when the time comes to replace my current MBP. The offerings in the PC world are not perfect for me but they suit me be…
At least it is a refreshing counterpoint to the "if it doesn't suit me, it can't suit anybody" sentiment that I've seen a lot of.
Re: Visual Studio for Mac
#130Earlier quoted context omitted.
You do know the difference between a text editor and an IDE? That's the difference between VS Code and VS.
Do YOU know the difference? Would it hurt to be more concrete? I'm going to venture a guess based on my assumptions, which are probably wrong, but then we can at least start a discussion: -VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another -VS Code doesn't support runtime debugging (breakpoints) -VS Code doesn't have a visual editor -VS Code doesn't ha…
Disclaimer: I'm not using the C# extension
> VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another
F2 "Rename Symbol" (works on Go with gorename). Can't imagine using Roslyn doesn't (or won't soon enough) allow the same. From the readme:
Great C# editing support, including Syntax Highlighting, IntelliSense, Go to Definition, Find All References, etc.
> VS Code doesn't support runtime debugging (breakpoints)
It does. CMD+Shift+D goes to the Debug sidebar. CMD+Shift+P Debug shows a bunch of commands. From the readme:
Debugging support for .NET Core (CoreCLR). NOTE: Mono and Desktop CLR debugging is not supported.
> VS Code doesn't have source control integration
CMD+Shift+P git whatevs is used daily here as well as Ctrl+Shift+G for the git sidebar that can show (editable) diffs. Both the gutter and scroll bar are annotated with git info.
> VS Code doesn't have an integrated build tool (MSBuild)
MSBuild comes with .Net Core and is (probably) invoked with the language-agnostic CMD+Shift+B (run build task). C# ext may have more.
> VS Code doesn't have NPM or Nuget integration
There are both NPM and NuGet extensions available.
Now of course if what you want is all of this nicely packaged and wrapped in a GUI, well, obviously VS Code is not an IDE (as VS is) but that's precisely its value proposition.