WHAT′S NEW IN RIDER (之三)

IntelliJ platform changes
Rider continues to take full advantage of its IntelliJ platform roots. In this release cycle, changes inherited from IntelliJ IDEA include:
•    Editor-based REST client based on scratch files with the .http extension. (The UI-based version of the REST client continues to be available, and even gets a few cosmetic updates.)
•    Version control updates including interactive rebase from Git log, preserving workspaces when switching between branches, and improved handling of Git and Mercurial merge commits.
•    Database updates: grouping data sources, XQuery/XPath coding assistance in.sql files via language injections, and more.
•    Docker support updates, most importantly revised Docker run configurations.

 
Settings
Rider's settings have been reworked in several ways:
•    You can now reliably export and import Rider settings via Import Settings,Export Settings and Manage Layers dialogs.
•    C# code style settings were extended with a Null Checking tab that helps choose a default null checking style in code that Rider generates for you.
•    Inspection severity configuration is now separated into per-language pages.
•    A new page with JetBrains Annotations settings was added under Inspection Settings.
Even more changes
•    Find Usages learns to work asynchronously to show available results while a search is still running, and offers a new grouping by usage type.
•    We have introduced a new Xcode keymap for long-time Mac users.
•    Designer files are now automatically regenerated on saving the associated .resx files.
•    Context menu on Solution Explorer nodes has been restructured for a clearer, more compact presentation of actions.
•    JetBrains annotations were ported to .NET Core, which makes entire categories of code inspections (nullability, LINQ, purity inspections) work more reliably.
Performance improvements
We have improved performance in many aspects, including:
•    Loading and reloading projects: thanks to a new asynchronous handling of MSBuild tasks, the synchronization stage of loading projects is now up to 5 times faster on large solutions that we used for testing.
•    Code completion performs faster on huge solutions.
•    In terms of debugging, the debugger launch time in some scenarios has been optimized, as well as rendering of large call stacks.