3 ms·
VS is nice and powerful, but ironically it needs Resharper to match a JetBrains IDE like IntelliJ for autocompletion/tooltips/navigation, which is severly lacki
by alkonaut 11y ago
VS is nice and powerful, but ironically it needs Resharper to match a JetBrains IDE like IntelliJ for autocompletion/tooltips/navigation, which is severly lacking in Visual Studio. That's one objection. The other problem with Visual Studio is that it's a beast. It takes multiple gigs of drive space (which of course suddenly became a problem when everyone's disks shrunk from 1TB to 128GB over night a couple of years ago, at the same time VS grew to around 15GB...). This is being worked on, but it will be a few more versions until the installer is good, and it will never be as small as an IDE that isn't carrying years of Windows legacy stuff. In short: VS is one of the best IDE's out there, but it would be a lot better (At C#) if it contained ReSharper's features and weighed in at 1/10 of its size. And that is exactly what this looks like.
- pjmlp 11y agoOn the other hand, the debugging tools are great!
- ruraljuror 11y agoI like Resharper a lot, but I do found that a lot of the features I use in Resharper are baked right into VS. For example, in Resharper Ctrl + T navigates to a symbol by name. That is Ctrl + , in VS. The code analysis/improvements/suggestions is definitely great though, at least for a while.
- alkonaut 11y agoI haven't used a "naked" VS for a few versions, how long has it had proper giro type/file/symbol navigation?
- ruraljuror 11y ago2010 (improved in 2013) according to this blog post. https://blogs.msdn.microsoft.com/mvpawardprogram/2013/10/22/visual-studio-2013-navigate-to-improvements/ https://blogs.msdn.microsoft.com/mvpawardprogram/2013/10/22/...
- robwilliams 11y agoI've never used Resharper but Visual Studio's Intellisense is incredibly powerful. What's lacking in its autocomplete support?
- to3m 11y agoI'm not the same guy, but what I've found: - No substring completion (e.g., like emacs's ido-mode), no fuzzy completion (e.g., like various JS-based editors), no acronym completion (e.g., like emacs) - Navigation bar searches are shit. You have to select namespace, then class, then symbol, and there seems to be no keyboard shortcut for any of this stuff. It should present a list of entities in the file, display fully-qualified name of each, and let one search that list using the search mechanisms - Class view searches aren't great. They solve many of the above two problems (the full list of entity names is searched, and it finds by substring), but the results don't update in real time - Very hard to find files. Say you have a massive project with loads of solution folders and you need to find that file that's got the name "ProductScreen" in it - well, good luck! There's something I've seen some people do with the toolbar-based Find in Files widget, but that only searches by prefix, which is useless, because so many projects have a mandatory prefix on their file names When I was a regular Visual Studio user - less Windows work of late means I've mostly been using emacs - I used to use Visual Assist (http://www.wholetomato.com/ http://www.wholetomato.com/), an addin that improves the above functionality a bit. Visual Assist's code completion is a bit intrusive, but it does the acronym completion thing; for navigation, its navigation bar replacement lets you search fully-qualified names by substrings, its class view-style functionality updates the symbol list (searched by substring) in real time, and you have something similar for finding files as well. All of this stuff is great for finding your way quickly around an unfamiliar project - i.e., any project with more than 15 programmers, even after you've been working on it for 2 years. And even when you know exactly what you want, at least you don't have to keep typing in that stupid project-specific prefix everywhere. (I'm happy for the Visual Assist people that MS hasn't just copied their functionality exactly and totally put them out of business in one go, but it does make me a bit mistrustful of the Visual Studio UI team's judgement.)
- henrikschroder 11y ago