Rider EAP 24 includes performance fixes, F# Interactive
We have a new Rider EAP build for you today. Highlights of this build include performance and memory consumption fixes, Unity support improvements, and F# Interactive, accompanied by a few dozens of bug fixes.
Last week, we were put to shame due to a performance impact that Rider was incurring on RavenDB development:
— ayende (@ayende) June 21, 2017
Investigating the report revealed a set of problems, and although we’re unable to fix all of them right away, we did get rid of some:
- We modified the caching workflow so that files that are not part of a solution aren’t processed multiple times.
- We fixed a memory problem whereby the file structure model would be stored in memory even without opening the Structure view. This should help tone down memory consumption when opening large files in the editor.
- We optimized handling of external file changes, such as those that occur when you switch to a different Git branch.
- We made the Unity plugin behave, and it should no longer track file changes in projects that have nothing to do with Unity (on larger solutions, this alone is expected to cut loading times down by 5-10 seconds.)
The RavenDB case helped reveal more problems that will take more time to get addressed, which means we’ll be planning some architectural changes in ReSharper and Rider for further releases later this year.
You can now use the F# Interactive tool window for F# scripting: both without ever leaving the console and by throwing selected lines or selections from the text editor. There’s a separate keyboard shortcut to send to F# Interactive, and the action is also available in Rider’s mainstream Alt+Enter menu:
Unity support changes
First off, there’s something that we had done for EAP 23 but didn’t have a chance to talk about. We have recently refactored two separate Rider plugins for Unity into one plugin that:
- Is bundled with Rider;
- Installs a Unity Editor extension once you open a Unity solution in Rider.
In other Unity news, when opening a Unity solution, you will be prompted to disable Rider’s auto-save feature to prevent frequent recompilation, and Rider will in fact make these configuration changes for you:
- In the application menu, we have merged File > Open with File > Recent Projects for a single list that works whether or not you have a history of opening the solution that you’re currently looking for.
- Web.config and app.config received improved support with validation and completion for tags and attributes, as well as automatic insertion of required config sections.
Download and try
Please download the latest Rider EAP build and give it a try. Do submit any exceptions that you encounter: it’s essential for us to have a profile of current exceptions before we switch to production builds as we wrap up for the release.
Subscribe to Blog updates
Thanks, we've got you!
Eager, Lazy and Explicit Loading with Entity Framework Core
Entity Framework Core (EF Core) supports a number of ways to load related data. There’s eager loading, lazy loading, and explicit loading. Each of these approaches have their own advantages and drawbacks. In this post, let’s have a quick look at each of these ways to load data for navigational prope…
OSS Power-Ups: bUnit – Webinar Recording
The recording of our webinar, OSS Power-Ups: bUnit, with Egil Hansen and Steven Giesel, is available. This was the twelfth episode of our OSS Power-Ups series, where we put a spotlight on open-source .NET projects. Subscribe to our community newsletter to receive notifications about future webi…
Accelerating Your Testing Workflow with Unit Test Creation and Navigation
Unit tests play an important role in our daily development workflow. They help us ensure our codebase's correctness when writing new functionality or performing refactorings to improve readability and maintainability. In the process, we often create new test files that accompany the p…
Introducing Predictive Debugging: A Game-Changing Look into the Future
With the introduction of debugging tools, software developers were empowered to interactively investigate the control flow of software programs to find bugs in live environments. At JetBrains, we've always strived to improve the art of debugging. Besides the more standard things you expect from a de…