![]() Also Visual Studio uses the bold font to highlight all parent nodes which lead to a cluttered result. On the other hand the rows are confusing and useless (Group by mode is: Project, Containing type, Containing member). Moreover Visual Studio uses code highlighting in this panel which is neat. But I found the Resharper way of presenting usages much clearer (left side on the screenshot below) than the Visual studio way (right side on the screenshot below).Īgain my opinion is subjective and I understand if some Visual Studio users prefer the pruned Visual Studio way of presenting usages. Both Resharper and Visual Studio proposes this feature. Many times a day as a developer, we need to locate all references of a code element. If the identifier is declared in more than one namespace the user experience falls back to the Ctrl+dot one presented above: ![]() Update: Visual Studio 2022 now automatically adds the using clause upon copy-pasting, so cool!!! ![]() Since copy-pasting is a common action, this missing feature is one of the tiny annoying thing that makes me goes to Visual studio > Option> Resharper > Resume Now. This is less immediate than the Resharper way. Then the user has to move the caret over the error and then press (Ctrl+dot), a well known keyboard shortcut for any seasoned Visual Studio user. On the other hand, when some code gets copy-pasted Visual Studio takes a second to underline the error with a squiggle. Thus this preemptive tooltip that reminds the ( Alt+Enter) keyboard shortcut is the right balance IMHO. The tool could import the using clauses itself but this would sound awkward and in some cases some choices have to be made if several types with the same name are declared in different namespaces. One thing that I love with Resharper is that when some code gets copy-pasted, the tool almost forces the user to accept importing the missing using clauses. Nevertheless I feel that only a few improvements in Visual Studio could lead me to live without Resharper. Hence one might disable Resharper periodically to check if he can live without it to get a slimmer and faster Visual Studio.Īs a more than a decade Resharper user, a more than two decades Visual Studio user and a Visual Studio extension author, my opinion is necessarily biased. If you are not aware of these improvements you can read these two articles that illustrate them: Top 10 Visual Studio Refactoring Tips and 10 Visual Studio Navigation Productivity Tips. Since the introduction of the Microsoft Roslyn compiler in 2015, the Visual studio engineers made massive progresses in areas like code analysis, refactoring, navigation and searching. However there are real hopes that soon Resharper in VS will get faster, both because Visual Studio 2022 will run in a 64 bits process with (almost) unbounded memory, and because Jetbrains engineers are currently moving Resharper out-of-proc. Resharper is a great Visual Studio productivity extension but on the other hand it slows down significantly the IDE, especially when working with large solutions.
0 Comments
Leave a Reply. |