ReSharper (and Rider) have always provided a wide range of code inspections to notify us about redundancies in code, potential code quality issues or common practices. In the next 4 blog posts, we will dive into a bunch of new … Continue reading
Along with the latest releases of ReSharper, we have made Code Cleanup part of the ReSharper Command Line Tools. These tools allow us to run several ReSharper features from the command line or as part of continuous integration. Two tools have been there for … Continue reading
Our previous blog post showcased two great web developer tools in Rider 2017.3: LiveEdit and Spy-JS. Let’s look at two more tools Rider gets from WebStorm: a new editor-based HTTP client and a preview panel for SVG files. This post is part of a … Continue reading
In the previous post of our series exploring WebStorm functionality in Rider, we looked at improvements in our Angular and Vue.js support, as well as added support for –watch in Jest and Mocha test runners. In this post, we want to introduce you to … Continue reading
Thanks to the concept of Run/Debug configurations, Rider makes it easy to switch between projects we want to debug in the IDE. Using compound Run/Debug configurations, we can even debug multiple projects at the same time (see our debugging series for … Continue reading
The Rider team has been on fire lately, and in an unprecedented sprint, the folks have just come up with their third major release in the span of 5 months: please welcome Rider 2017.3 RTM.
In our previous posts, we looked at a few examples of the various improvements we made to the code formatting engine in ReSharper 2017.3 EAP and Rider 2017.3 EAP. While we now have great control over how our source code is formatted, … Continue reading
In our previous post, we looked at how we can use different code styles for different blocks of code in ReSharper 2017.3 EAP and Rider 2017.3 EAP. In this post, we will look at some other improvements to the code formatting engine, … Continue reading