The JetBrains Blog

The second minor update of Rider 2018.1 is available for download! You can install this bug-fix update either via Toolbox App, or as a patch for Rider 2018.1 (use Help | Check for Updates), or otherwise just get an installer from our website. Rider 2018.1.2 fixes the annoying code typing and comp…

Sometimes even a bug fix update needs a bug fix update. Well, today is the day: we welcome you to upgrade to ReSharper Ultimate 2018.1.2. If you are experiencing slow typing, or if the completion popup displays slowly for you in ReSharper 2018.1.1 build, the new build comes to the rescue. Apar…

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 post, we are going to …

A polished version of Rider 2018.1 is ready. Just click download to get the latest Rider 2018.1.1 bug-fix update working on your machine. Among the many bug fixes, you will find some new features as well. Here are some highlights of this build we have prepared for you: (more…)…

Hello from JetBrains! We have something interesting for you today. A few moments ago, we published the first bug fix update for our first release of the year - ReSharper Ultimate 2018.1.1. Below, you can find a list of the notable changes: (more…)…

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 features, too, using over 2400 inspections coming from ReSharper and …

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 validating our code using over 2400 inspections coming from ReSh…

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 make use of Rider's code analysis to spot errors before comp…

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 Analysis works with all languages supported by Rider and…