I do wish it had a global symbol search, similar to Sublime's (cmd+shift+r). It's indispensable for code navigation.
Visual Studio Code 1.0
131–140 of 487 posts
Re: Visual Studio Code 1.0
#132Earlier quoted context omitted.
UWP has the latest version of XAML, implemented natively this time and with a faster rendering backend. WPF lives on in spirit.
Even WinForms is still around somehow, though in a "cannot be killed" legacy Form as opposed to WPF having a direct descendant in UWP. Silverlight, though...
WPF > Silverlight > UWP
All your skills are transferable.
Re: Visual Studio Code 1.0
#133Interesting that they decided to release 1.0 before sorting out the coreclr/dotnet story. My understanding is that Mono is still the best way to write C# with VSCode, even on Windows.
Re: Visual Studio Code 1.0
#134VSCode has done the thing that nobody expected MS to do, change the way code was written on Unix/Linux. I love linux/unix, but the problem always was with the lack of an awesome text editor cum IDE, yep there is eclipse but it is too clunky, I do not like sublime as it isn't FOSS (call me crazy), gedit took way too much memory, geany is fast and mean but the UI sucks plus functionality isn't that great. Enter VSCode,…
What was lacking in Atom for you?
Also: Doesn't ask me to save my unsaved files when I close the editor. Sublime Text called this feature "hotexit", but in Atom there's no way to disable it.
Re: Visual Studio Code 1.0
#135The one thing that prevented me from switching to VSCode last time I tried it was the lack of projects management (e.g. a project remembers what files were open, what folders are associated with it, and you can quickly switch between projects, like the CTRL+ALT+P list in Sublime Text). Is there such a feature now?
Re: Visual Studio Code 1.0
#136What's so exciting about this? As far as I can tell it's just a pretty basic editor. Is there anything innovative in it?
Why the downvotes? Am I missing something here?
Re: Visual Studio Code 1.0
#137I'm your standard unix greybeard, the sort that uses org-mode to outline-structure their emacs config (that's actually what I do, not even a hypothetical), so I approached VSCode with skepticism. I have actually been really impressed. It's fast and responsive, even on Linux, and the TypeScript tooling is fantastic. I think with a bit more UI work (like vi keybindings) it could potentially become my preferred editor.
Re: Visual Studio Code 1.0
#138Re: Visual Studio Code 1.0
#139Does anybody else use several editors all the time? I use Emacs, Vim, Eclipse, Atom, and Intellij. I don't stick to one. I wish I could stick to one editor but there is always some editor that does a way better job at a particular task. Each editor has its killer feature. I have tried turning emulation of emacs/vim on many editors to provide consistency and its never been really good. Thus I have several "default" ke…
Re: Visual Studio Code 1.0
#140Earlier quoted context omitted.
Agreed, IntelliJ IDEA is so good I can't really use other editors for projects. For editing regular files outside of a project I still use vim or TextEdit/Notepad. I prefer Intellij so much I use CLion instead of Xcode on OS X and Visual Studio on Windows 10.
I didnt think Clion worked with MSVC?
I can build .exe's that run fine on Windows this way and executables that run on OS X (using the X-Code supplied compiler and build tools that CLion depends on for OS X). I can get qt, wxWidgets and GLFW UIs working for both platforms from the same code base with CLion.