This is an experiment that is doomed to failed, but given that I just setup a new VS 2017, I decided to see how it would feel to run it without ReSharper and how it impacts my workflow. Please note that this is very much not an unbiased review. I have been using ReSharper for my day to day coding for over a decade, and the workflow it enables is deeply rooted in how I work. I’m going to ignore any differences in key bindings, as irritating as that can be, in favor of just looking at different features. So far, I spent a couple of days trying to work on VS 2017 without ReSharper. It has been quite frustrating, but I was able to sort of limp along.
I most certainly felt the lack. My hope was that I would be able to see the promised performance improvements without it, and then consider whatever it is worth it. That wasn’t the case. As you can see, ReSharper is not installed, but I managed to get VS into a hang several times.
It seems to happen with NuGet, or when trying to use the Test Explorer and a few times when I was trying to edit code while the solution was compiling. Without any meaningful order, here are the things that I really felt the lack of. • Go to definition with automatic decompile is something that I apparently use a lot more than I expected. It helps figuring out what I can expect from the method that I’m looking at, even when it is not our code that I’m looking at.
If you purchased a license of Visual Assist, or renewed maintenance, before mid-February 2019, you received a two-line activation key that identifies a license, user count, term of software maintenance, and hash-code that activates a genuine copy of Visual Assist.
• Refactor method ignoring whitespace lets me just write a statement and it becomes a method name. This is actually quite nice. • Quick docs in R# is very nice, that is, the ability to hit Ctrl+Q and get the docs for a method is something that I seem to be using a lot. This is important because I can quickly check the docs (most often, what conditions it has for returning, or specific arguments. The key here is that I don’t need to leave my current context. I can Ctrl+Q, peek at the docs, and then move on.
Skachatj kivi koshelek na kompjyuter dlya vindovs 7 days. • Extract variable isn’t there, and so are a lot of the refactoring that I’m used to aren’t there or are hardly accessible. • IntelliSense is also a lot less intelligent. Being able to write a method and just Ctrl+Space all the parameters because R# can fill the context is very useful.
• Ctrl+N, (symbol search) is also a LOT more useful. I’m familiar with the Ctrl+; to search solution explorer, but the features don’t compare. In one case, I get live feedback, which means that I don’t have to remember nearly as much about the symbol that I’m looking for.
On the other hand, I have to write it and hit enter to see the results. There is also an issue with the presentation. Solution explorer is really poor model for it. There is a lot of wasted space in the VS model versus the R# model. • Update: I have since learned about VS' Ctrl+, feature, and that seems much nicer, and it also does auto peeking, which I like. In general, to be honest, R# feels smarter (remember, I’m biased and likely work to the strengths of R#).