Author Archives: Maarten Balliauw

Performance improvements in ReSharper 2018.1 and 2018.1.1

In previous posts of our series about ReSharper performance, we’ve looked at a number of high-level, architectural improvements JetBrains is making in terms of performance. We also discussed software tends to accumulate smaller, local performance problems over time. In this … Continue reading

Posted in How-To's | Tagged , , , , , , | 11 Comments

Component composition, just-in-time-compilation, the UI thread – ReSharper performance series

In the previous post of our ReSharper performance series, we have seen that it makes a lot of sense to explore running it as a separate process. This brings many benefits: both Visual Studio and ReSharper would run in their … Continue reading

Posted in How-To's | Tagged , , , , , , | 15 Comments

Taking ReSharper out of process – ReSharper performance series

In the previous post of our ReSharper performance series, we looked at Visual Studio and ReSharper complexity and history, and determined that one of the reasons for degraded performance lies in Visual Studio being a 32-bit process. In this post, … Continue reading

Posted in How-To's | Tagged , , , , , , | 27 Comments

Introducing the ReSharper performance series

With every ReSharper update, we get questions around performance. Some users notice a slightly slower solution load, others see a minor indexing lag, and others get bugged by a yellow notification bar stating “Extension ‘JetBrains ReSharper Ultimate’ likely caused 9 … Continue reading

Posted in How-To's | Tagged , , , , , , | 42 Comments

Consistent code bases using Rider code analysis

In our series about Rider‘s code analysis, we’ve seen what it is and how it works, and looked at various examples of inspections that can spot warnings and errors in our codebase. Rider helps us learn common practices and language … Continue reading

Posted in How-To's | Tagged , , , , , | 4 Comments

Learning best practices and language features using Rider code inspections

In the previous posts, we have seen how Rider‘s code analysis works and looked at how we can do things like spotting warnings and errors even before compiling and running our application. Rider helps us with such things by continuously … Continue reading

Posted in How-To's | Tagged , , , , , | 4 Comments

Using Rider to spot errors before our application runs

In the previous two posts, we have seen how Rider‘s code analysis works: it continuously validates our code, analyzing it with over 2400 inspections coming from ReSharper and from IntelliJ-based IDEs. In this post, we’ll look at how we can … Continue reading

Posted in How-To's | Tagged , , , , , | 1 Comment

Solution-wide analysis in Rider

In a previous post, we looked at the basics of Rider‘s code analysis. We’ve seen that Rider continuously runs over 2400 inspections and validations on our code, informing us about potential issues and improvements while we are writing it. Code … Continue reading

Posted in How-To's | Tagged , , , , , | 4 Comments

Introduction to code analysis in Rider

One of the strengths of Rider is code analysis. Rider comes with over 2400 code inspections that analyze our code at design time, allowing us to instantly see any errors, problems or potential improvements – whether in the current file … Continue reading

Posted in How-To's | Tagged , , , , , | 2 Comments

Better null checks, string formatting and path completion with JetBrains Annotations

In the previous blog post of our series around using JetBrains Annotations to improve Rider (and ReSharper’s) code analysis, code completion and navigation, we looked at some background: what are these annotations? And how do we add them to our source … Continue reading

Posted in How-To's | Tagged , , , , | 2 Comments