Rider Changelog

What's new in Rider 2024.1 Build 241.14494.307

Apr 9, 2024
  • New Monitoring tool window:
  • The latest version of Rider introduces the Monitoring tool window – a new feature to monitor your application’s performance and gather key metrics during running or debugging. Learn more about the insightful new tool from this blog post.
  • The Monitoring tool is designed to integrate seamlessly with Rider’s built-in performance and memory profiling tools – dotTrace and dotMemory. Scroll on to read about the new performance and memory profiling capabilities you can enjoy in Rider 2024.1.
  • New features for the debugger:
  • The latest major update comes with a host of improvements for the debugger. The most exciting and long-anticipated one is the collections visualizer. The collections visualizer provides graphical representations of collections (arrays, lists, dictionaries, and other enumerable types), allowing you to expand and collapse elements, view individual values, and easily navigate through the data structure. You can even plot the values on a graph!
  • Another enhancement for the debugger is the visualization of stepping time. When debugging an application with Rider, you’ll now see an inline hint displaying the time elapsed between the last and current breakpoints. Excessively long stepping time could indicate performance issues in your code that you might want to explore further with the built-in dotTrace and dotMemory profilers.
  • Rider 2024.1 also brings the Hot Reload functionality for running and debugging Blazor WebAssembly (WASM) applications. Learn more about this and other Blazor WASM development workflow improvements in Rider 2024.1 from this blog post.
  • You can find the complete list of updates for the debugger on the What’s New in Rider page.
  • UX/UI enhancements:
  • Sticky lines in the editor:
  • To make your experience of working with large files and exploring new codebases easier, Rider 2024.1 introduces sticky lines. This feature keeps key structural elements, like the beginnings of classes or methods, pinned to the top of the editor as you scroll. This way, scopes always remain in view, and you can quickly navigate through the code by clicking on one of these pinned lines.
  • Updated New Project dialog:
  • We have thoroughly reworked the New Project dialog to make new projects easy to configure. Here’s what you can expect from the updated dialog:
  • Support for all .NET-specific project configuration options (for example, a check-mark for progressive web apps when creating a Blazor WASM application).
  • Support for parameters in custom project templates.
  • The ability to install a solution’s target SDK right from the dialog.
  • The ability to install the appropriate MAUI workload from the dialog.
  • Other improvements:
  • We’ve added the ability to decrease the scaling of the entire IDE down to 70%, giving you more flexibility.
  • This build brings an overhauled Terminal tool window that gains both visual and functional enhancements. It has been designed to elevate the convenience and simplicity of terminal-based tasks. Click here to learn more.
  • C# support:
  • Rider 2024.1 comes with the following improvements to C# language support:
  • More conversions to collection expressions.
  • A new Collection was modified inspection.
  • Updates to Generate | Formatting Members.
  • Enhanced support for disposable resources in async methods.
  • Updates to the Change Signature refactoring.
  • Updates to the Make Static refactoring.
  • Faster Rename and Move to Another Type refactorings.
  • High resource utilization mode in solution-wide analysis.
  • For the details on the C# updates, please visit the What’s New in Rider 2024.1 page.
  • Game development:
  • Every major update to JetBrains Rider comes with a variety of enhancements for game development. The 2024.1 release is no exception, and you can read about all of the updates on the What’s New in Rider page.
  • Unity’s Odin Inspector support:
  • We’ve been working with our friends at Sirenix to provide support for the popular Odin Inspector Unity asset. Rider will recognize and highlight fields and properties serialized by Odin Inspector, provide completion and inspections for group names in layout attributes, and show previews of Odin’s GUIColor class. It will also recognize Odin’s range attributes and use those values in Rider’s own integer value analysis, warning you if a value goes out of range.
  • Support for Unreal Engine’s Slate UI framework:
  • This release adds support for Unreal Engine’s Slate UI framework, teaching Rider how to use the Go to Definition and Find Usages commands, as well as the Rename refactoring to rename the symbols declared by the Slate macros.
  • Rider will now format Slate DSL code correctly when invoked directly as a reformat action or as you type.
  • Rider 2024.1 also offers a few notable updates to C++ language support. Rider’s C++ support is powered by ReSharper C++. Check out What’s New in ReSharper C++ 2024.1 for more details.
  • Web development:
  • Here are just a few of the updates for web development we’re shipping with this release:
  • Resolve references for @addTagHelper and @removeTagHelper directives.
  • Generate additional files like .razor.cs, .razor.css, .razor.js when generating Blazor Component file templates.
  • Use quick-fixes for React props and state creation.
  • For more information on the improvements in web development, please refer to this page.
  • Plugins:
  • Performance and memory profiling :
  • The built-in dotTrace and dotMemory profilers now support MAUI (desktop only) and .NET macOS applications. Click here for more information on the available profiling modes.
  • dotMemory inside Rider 2024.1 now offers support for Frozen Objects Heap (FOH). This enables dotMemory to perform a more detailed analysis of memory used by immutable objects in the FOH, boosting the optimization of memory usage.
  • To learn more about the latest updates to the .NET profiling tools, visit the What’s New in dotMemory and What’s New in dotTrace pages.
  • .NET Aspire :
  • The .NET 6 SDK introduced .NET Aspire – a new approach to tackling the complex issues around building distributed applications on the .NET stack. In response to this innovation, we’re offering new integrated tooling – the .NET Aspire plugin for Rider.
  • AI Assistant:
  • In version 2024.1, JetBrains AI Assistant has been unbundled and is now available as a separate plugin. This change is driven by the need to offer greater flexibility in decision-making regarding the use of AI-powered technologies, providing more control over your preferences and requirements in working environments. AI Assistant still requires an active JetBrains AI subscription.
  • The latest update to JetBrains AI Assistant for Rider introduces two new features: Explain with AI and Rename with AI. More on that here.
  • Other notable updates:
  • Rider 2024.1 contains a multitude of enhancements for version control. Click here to learn more.
  • The new Azure Toolkit for Rider plugin is now available and can be downloaded and installed inside JetBrains Rider. You can download the plugin from JetBrains Marketplace.
  • We’ve enhanced support for GitHub Actions in this release, with a particular focus on CI/CD workflows. Click here to learn more.
  • The Assembly Explorer inside Rider now supports the WebCIL packaging format for WebAssemblies.
  • Following the lead of ReSharper, Rider also receives an upgraded spelling and grammar checker. The new spellchecker supports over 20 languages and catches natural language errors within programming languages supported by Rider.

New in Rider 2024.1 Build 241.14024.36 EAP 7 (Mar 1, 2024)

  • More suggestions to convert code to collection expressions
  • New Collection was modified inspection
  • Updates to Generate | Formatting Members
  • Refreshed product icons
  • New Explain with AI button to clarify exceptions and error messages
  • The bundled Kubernetes plugin

New in Rider 2024.1 Build 241.13688.41 EAP 6 (Feb 27, 2024)

  • Updated New Project dialog.
  • Blazor WASM Hot Reload for debugging.
  • Enhanced support for disposable resources in async methods.
  • Custom naming rules in Settings.
  • Version Control Systems improvements.

New in Rider 2024.1 Build 241.12662.57 EAP 5 (Feb 16, 2024)

  • A collections visualizer for the debugger.
  • Sticky lines in the editor.
  • Enhanced GitHub Actions support.
  • Support for the WebCIL packaging format for WebAssemblies in the Assembly Explorer.
  • More ways to access and build type dependency diagrams.

New in Rider 2024.1 Build 241.11761.31 EAP 4 (Feb 9, 2024)

  • New Monitoringtool window.
  • Blazor WASM Hot Reload in Run mode.
  • Assembly resolve for addTagHelper directives.

New in Rider 2024.1 Build 241.10840.28 EAP 3 (Feb 2, 2024)

  • The option to show tool window names in the side toolbars
  • The option to scale down the entire IDE
  • Stepping time and inline breakpoints for debugging

New in Rider 2023.3.3 Build 233.14015.60 (Jan 23, 2024)

  • MAUI projects can once again be deployed to physical iOS devices. [RIDER-76794]
  • The Export to file action works correctly for type dependency diagrams. [RIDER-103400]
  • Text in the Editor window no longer freezes when being scrolled. [RIDER-103794]
  • Xamarin.Android Designer now works as intended. [RIDER-99102]
  • Rename works correctly for references between files in Rider 2023.3. [RSRP-495217]
  • Abbreviations are no longer falsely flagged as spelling mistakes. [RSRP-495107]
  • String length checks for Entity Framework entities no longer generate incorrect hints when MaxLength is set by static and constant values. [RSRP-495160]
  • Primary constructor attribute inheritance no longer triggers false positive warnings. [RSRP-495253]
  • The IDE’s suggestion to dispose of the IEnumerator GetEnumerator() call result was retained, while the corresponding quick-fixes were adjusted. See this comment for details. [RSRP-494839]
  • Error executing shell command pm list packages no longer occurs when attempting to debug on a physical Android 13 device. [RIDER-81549]
  • The IDE no longer sends erroneous update notifications for disabled plugins. [IDEA-273418]
  • Marking GitHub pull request files as “reviewed” works as expected. [IDEA-338906]
  • The search functionality in the Emoji & Symbols popup dialog works on Linux. [IDEA-327171]
  • The IDE correctly displays the chosen file in the Commit dialog when executing the Commit File action for one of the modified files. [IDEA-336983]

New in Rider 2023.3.2 Build 233.13135.100 (Dec 20, 2023)

  • The IDE is once again able to debug .NET MAUI 8 applications. [RIDER-102944]
  • Rider can run, debug, and locally deploy to an IIS server. [RIDER-101511]
  • Code highlighting no longer goes out of view when typing or pasting code in Unreal Engine solutions. [RIDER-49172]
  • Rider no longer freezes when Refresh Unity Assets is initiated. [RIDER-102905]
  • Self-contained deployment once again works as intended. [RIDER-102217]
  • The Commit window no longer gets stuck when the cleanup option is activated. [RIDER-97983]
  • The Backspace key no longer malfunctions when trying to erase text in some textboxes. [RIDER-100330]
  • Pop-up menus appear in appropriate places inside remote development environments. [RIDER-100330]
  • Editing SQL in C# verbatim interpolated strings no longer causes rendering issues. [RIDER-103274]
  • Git Version Control now works correctly in cases where there’s more than one instance of Rider open for the same branch. [RIDER-100680]
  • Xamarin.Android Designer works correctly. [RIDER-99102]
  • Renaming a project does not interfere with code highlighting. [RIDER-99162, RIDER-102566]
  • Attaching the debugger to an SSH Docker container works as intended. [RIDER-103009]
  • We’ve fixed the issue causing the IDE to display a blank window when opening a second project in full-screen mode on macOS. [IDEA-339992]
  • This build also includes fixes for solution-wide analysis, primary constructor inspections and refactorings, as well as several issues associated with Entity Framework inspections. For more information please see the ReSharper section in this blog post.

New in Rider 2023.3 Build 233.11799.261 (Dec 7, 2023)

  • AI Assistant is out of preview:
  • AI Assistant, first introduced with our previous release, has now moved beyond the technical preview stage and features a host of exciting improvements, such as:
  • A context-aware AI chat.
  • Better project awareness for AI Actions.
  • AI-powered multiline code completion.
  • In-editor code generation.
  • Documentation generation.
  • Unit test generation.
  • A Diff view for AI-suggested refactorings.
  • The ability to create a custom library of prompts.
  • NET 8 SDK support:
  • Rider 2023.3 officially provides support for the .NET 8 SDK, including:
  • Updated project templates.
  • The ability to create, run, and debug projects targeting the new SDK.
  • New C# 12 features, including primary constructors, interceptors, and alias directives to reference any type.
  • Support for F# 8 features, namely shorthand lambda expressions, nested record updates, static interface members and let bindings, and more.
  • Support for @ variables.
  • Support for Identity API endpoints.
  • Support for cross-platform Hot Reload.
  • C# 12 support:
  • With its latest release, Rider extends the list of supported C# 12 features, namely primary constructors, collection expressions, interceptors, and others.
  • Check out this series of blog posts we’ve put together exploring these language support updates in Rider 2023.3 and ReSharper 2023.3:
  • Primary Constructors
  • Interceptors – Coming Soon
  • Collection Expressions – Coming Soon
  • Improved experience running multiple projects:
  • The new Run Multiple Projects feature in Rider 2023.3 allows you to set up custom multi-launch configurations to ensure all of your solution’s dependencies are handled flawlessly.
  • Type dependency diagrams:
  • Type dependency diagrams in Rider 2023.3 provide a visual representation of how different elements in the codebase interact with each other, making it easier to grasp your project’s design and adding clarity to debugging.
  • Predictive debugging:
  • Predictive debugging is a new advanced debugging mode for Rider that predicts potential issues in your code and alerts you to them without the need to execute the code.
  • In addition to gaining a predictive debugging mode, Rider 2023.3 also now boasts a new Modules view that lets you inspect the dynamic link libraries (DLLs) and executables that your app uses.
  • Creating and navigating through unit tests:
  • You can now easily navigate and create tests for your production code using Rider. With this release, we’re also introducing the ability to generate the tests using AI Assistant.
  • Performance enhancements:
  • Rider 2023.3 puts you in control of the amount of resources to be allocated to solution-wide code analysis. You can now choose between Low, Moderate, and High modes of resource utilization.
  • UX/UI:
  • The Run button in the main toolbar has been replaced with a Resume button during debugging.
  • Rider can now help you quickly create solution filter files to tailor your IDE’s Project view to the specific context you’re working in.
  • There’s now an option to hide the main toolbar in the default viewing mode to visually declutter your workspace.
  • The Speed Search functionality, allowing you to quickly navigate within tool windows and dialogs, is now available via a shortcut.
  • There’s a new product icon for Rider on macOS that matches the style guidelines of the operating system.
  • Game development:
  • Unity:
  • Rider 2023.3 comes with UI Toolkit support. The IDE will now show you where UI elements are used in UXML files, help you navigate from elements in UXML files to C# code, and provide code completion for UI elements in C# queries.
  • The latest update also contains shader variant support. A new optional preview feature allows you to select the keywords that are active while editing a shader file.
  • The debugging experience for Unity projects in Rider has been improved in several ways. We’ve also added plenty more small fixes and features, such as completion of semantics in HLSL code and fixes for both online help URLs for packages and incorrect warnings for certain DOTS scenarios.
  • Unreal Engine:
  • A significant new feature allows Rider to only recognize symbols from explicitly included files and ignore anything imported by pre-compiled header (PCH) files. This allows local builds to use PCH files for improved compilation speeds while ensuring correctness for CI build servers.
  • Web development:
  • The latest major update to Rider offers some handy tweaks for working with TypeScript, improved Angular support, and a number of other valuable enhancements.
  • Remote development:
  • A lot of effort has been put into improving the typing experience when using remote development in Rider 2023.3. The enhancements have made all aspects of typing in the editor more convenient, including code completion, context actions, and popups.
  • Frameworks and technologies:
  • Code completion for Central Package Management:
  • With this release, we’re introducing enhanced support for your CPM files with code completion features for NuGet package names and versions. These files now get the same support that was previously introduced for .csproj files.
  • Plugins:
  • For this release, the built-in performance and memory profilers inside Rider have both seen improvements to the way data is collected and presented. Click here to learn more about profiling using dotMemory and dotTrace inside Rider 2023.3.
  • Other plugin updates:
  • Dynamic Program Analysis now offers three new inspections for applications targeting the ASP.NET Core framework. Check out this blog post, which covers the new inspections in detail.
  • The Entity Framework Core UI plugin has been bundled, making the UI for EF Core commands available inside JetBrains Rider.
  • Other notable updates:
  • In Rider 2023.3, you are able to right-click inlay hints to reveal the context menu. You can also navigate to declarations from an inlay hint with Ctrl+Click.
  • The IDE now offers automatic code completion for URL path references.
  • Expanding the GitLab integration introduced with the Rider 2023.2 release, we’ve added support for GitLab snippets. Now, you can create public or private snippets directly within the IDE.
  • Starting with Rider 2023.3, it is now possible to attach to a process inside a container for debugging. More on that here.
  • Rider 2023.3 brings a new security inspection feature designed to make published vulnerabilities more apparent and easier to understand.

New in Rider 2023.2.3 Build 232.10203.29 (Nov 5, 2023)

  • Rider once again correctly displays Unity’s declarations on macOS. [RIDER-93883]
  • The ability to deploy and debug to physical iOS 17 devices using Xamarin has been restored. [RIDER-99240]
  • The list of directories is again correctly rendered in the Solution Explorer. [IDEA-326394]
  • Absolute directory paths in the Commit tool window no longer take up too much space as a result of redundantly replicating parent paths. [IDEA-326271]
  • We’ve addressed the issue that made it impossible to copy text from a local machine’s editor and paste it into the editor on Windows Remote Desktop. [IDEA-313776].
  • This build also includes support for @ variables in HTTP Client. [RIDER-98743, IDEA-320823]

New in Rider 2023.3 Build 233.9802.20 EAP 3 (Oct 17, 2023)

  • Support for rootless containers
  • Improvements to global usings support
  • Enhanced JSON request body completion in the HTTP Client
  • Automatic code completion for URL path references
  • Code completion for Central Package Management
  • Updates to the AI Assistant plugin

New in Rider 2023.3 Build 233.9102.265 EAP 2 (Oct 10, 2023)

  • All-in-one diff viewer
  • Debugger data flow analysis
  • An enhanced user experience with Speed Search
  • Entity Framework Core UI plugin bundled with Rider
  • Improvements to coding assistance for Unity’s UI style sheets
  • Three new inspections in Dynamic Program Analysis for applications targeting the ASP.NET Core framework

New in Rider 2023.2.2 Build 232.9921.83 (Sep 27, 2023)

  • The IDE no longer generates critical failure errors due to a StackOverflowException being thrown during code analysis of the ConditionalTernary operator. [RSRP-493897]
  • Code analysis now correctly processes the replacement of tag helpers in _ViewImports.cshtml. [RSRP-493577]
  • The VCS widget now initializes correctly for Unreal Engine projects opened via .uproject or .uprojectdirs. [RIDER-95512]
  • The IDE no longer generates a new blank line in the .csproj file after a new folder is created inside the project. [RIDER-97746]
  • Correct file layout is maintained for files containing custom HasAttribute tags. [RSRP-493807]
  • Creating a new file for a Unity project from the Editor no longer causes Rider to crash. [RIDER-97905]
  • The Find in Files command highlights and sorts as intended for projects opened as a directory. [RIDER-98094]
  • macOS system shortcuts are no longer prioritized over the IntelliJ IDEA-based IDEs’ keymaps. [RIDER-97892]
  • The issue causing performance degradation when working with Markdown files containing tables has been resolved. [IDEA-326905]
  • The IDE no longer hangs on the splash screen because of the Exception in thread “AWT-EventQueue-1” error. [IDEA-314813]
  • The IDE now preserves the EditorConfig formatting properly again.[IDEA-326450]
  • The IDE no longer displays irrelevant GitLab merge request pipelines. [IDEA-326509]

New in Rider 2023.3 Build 233.6745.316 EAP (Sep 26, 2023)

  • Support for C# 12’s ability for alias directives to reference any kind of type.
  • Improved overall support for aliases, including new inspections, quick-fixes, and context actions.
  • New inspections for usages of methods in Entity Framework-related code that could potentially produce runtime exceptions.
  • Improved, CPU-friendly handling of injected languages.
  • Numerous UX/UI enhancements.
  • Support for GitLab snippets.
  • Improvements for game development.
  • The ability to attach to a process inside a container for debugging.

New in Rider 2023.2 Build 232.8660.212 (Aug 3, 2023)

  • C# updates:
  • Rider 2023.2 comes with the following improvements to its C# language support:
  • New inspections and context actions, improved typing assistance, and formatting options for working with raw string literals.
  • Inspections and quick-fixes for handling common Entity Framework issues.
  • Two new inspections and corresponding quick-fixes aimed at improving code readability when working with local functions.
  • Inspections for #nullable directives and NRT annotations.
  • Improved navigation from var declarations.
  • Primary constructor support for non-record classes and structs from the C# 12 preview.
  • Support for default parameter values in lambda expressions.
  • New code inspections designed for better control over object disposal.
  • Better C# discard support.
  • New inlay hints for improved code readability when working with tuple component names, null and default components, and deconstruction patterns.
  • Improved support for #pragma warning directives.
  • UX/UI improvements:
  • Reworked Build tool window:
  • In Rider 2023.2, we’ve reworked the Build tool window, both in terms of performance and UX/UI. Build output results are now loaded in a “lazy” manner, meaning only the build details you choose to look into from the event tree will be loaded and displayed. This makes the output far more CPU-friendly and easier to navigate.
  • New UI becomes the default look:
  • The latest version of Rider makes the reimagined IDE interface first unveiled in version 2022.3 the default for all new users. The new UI is sleek, modern, and highly customizable.
  • If you haven’t made the switch yet, we encourage you to give it a try by going to Settings / Preferences | Appearance & Behavior | New UI | Enable new UI.
  • Customization and streamlining:
  • The new UI is designed to eliminate visual clutter and streamline your workflow. Several updates in the 2023.2 release advance these goals:
  • Customizable project headers:
  • You can now navigate between all of your open projects by color! Headers come with predefined colors by default, but you can change them according to your preferences. You can even set up a custom icon for your solution as a finishing touch!
  • Improved main toolbar customization:
  • We’ve expanded the customization options for the new UI’s main toolbar. You can now use a drop-down menu to quickly choose actions that you want to add to the toolbar. To do so, right-click on any widget, select Add to Main Toolbar, and explore the available options.
  • Pinned run configurations in the Run widget:
  • To make managing multiple run configurations easier, we’ve implemented the option to pin preferred configurations in the Run widget. To add a run configuration to the Pinned section, open the kebab menu (three dots) next to its name and select Pin.
  • Other notable UX/UI updates:
  • Reworked hamburger menu in the main toolbar on Windows and Linux.
  • Light theme with light headers.
  • Single-click navigation between project directories.
  • File sorting by modification time in the Solution Explorer.
  • Native Linux header removed in the new UI.
  • Updated window controls on macOS.
  • AI Assistant [Limited access]:
  • With this release, we introduce a major addition to Rider – AI Assistant. The initial set of AI-powered features offers an integrated AI chat and weaves naturally into some of the IDE’s core user workflows. AI Assistant can analyze selected code, explain the meaning of a commit or a runtime error, generate documentation, and create Unity files written to your specifications.
  • Version control:
  • GitLab integration:
  • Rider 2023.2 introduces initial integration with GitLab, allowing you to work with the Merge Request functionality right from the IDE and streamline your development workflow.
  • Background commit checks:
  • We’ve reworked the behavior of commit checks for Git and Mercurial to speed up the overall commit process. Checks are now performed in the background after you commit but before you push.
  • Option to commit specific lines of code:
  • Rider 2023.2 introduces a highly anticipated feature that allows you to selectively commit specific parts of code chunks. To perform a partial commit, select the lines within a chunk and call Include these lines into commit from the context menu.
  • Performance:
  • With Rider 2023.2, we’ve revised our approach to caching the data required by the IDE to make its systems work. This revision, supported by myriad performance tests, resulted in a noticeable reduction in disk space consumption for each solution you open. In practical terms, it means less time spent doing disk input/output and faster loading times for solutions.
  • Game development:
  • Unity:
  • This is another release loaded with features for Unity development, with lots of improvements to the experience of editing ShaderLab files, additional updates to DOTS functionality, and better support for USS files.
  • Here are some key updates:
  • The new AI Assistant is aware of your development environment, providing Unity-specific responses and making relevant Unity API suggestions. AI Assistant can also generate a file written to your specifications for a Unity solution.
  • Improved ShaderLab support, including new typing assistance, live templates, improvements to viewing the file structure through breadcrumbs and the Structure tool window, and Ctrl+Click navigation to the name declaration of a shader or pass. Learn more from this blog post.
  • Support for Unity DOTS continues to expand. We’ve made some useful improvements to code generation for the Data-Oriented Tech Stack (DOTS) based on some great feedback from the Unity community. We’ve also introduced new file and live templates, in addition to extending Burst context analysis to more parts of your code.
  • Unreal Engine:
  • Rider 2023.2 is another great update for Unreal Engine support, with lots of updates to C++ as well as the introduction of support for Hot Reload and Live Coding, performance improvements for Blueprint indexing, and fixes and updates for Perforce support.
  • Some highlights:
  • This release features improved Blueprints indexing. By classifying Blueprints as secondary resources, Rider can now index all of your code before looking at your assets. This means you get access to the rich code editing experience sooner, while the assets are still being indexed in the background.
  • Rider now supports invoking Hot Reload and Live Coding from the IDE, allowing you to update your Unreal application while the editor is running.
  • We’ve improved the integration with Perforce, notably decreasing the time it takes to refresh the status of local files, among other fixes and updates.
  • .NET SDK:
  • Rider 2023.2 introduces a host of improvements for working with Roslyn analyzers and Source Generators, including the introduction of new project templates for them and a Reboot Source Generators button.
  • Docker support has been bolstered with the option to run Docker in fast mode, Docker Compose run configuration labels, and the ability to view the Docker log in the Console tab when debugging Docker containers.
  • Last but not least, Hot Reload is finally available for solutions targeting .NET MAUI!
  • Other release highlights:
  • The Find Usages functionality has received a functional upgrade in Rider 2023.2. Now, if you invoke Find Usages Advanced on a symbol (such as a method, class, or variable), the IDE will display a window where you can specify additional search criteria.
  • In Rider 2023.2, you can collect and analyze memory snapshots inside the IDE just as you can in the standalone version of the dotMemory profiler.
  • The Call Tree view now lets you group call stacks by individual threads, providing deeper insight into thread-specific performance issues.
  • Rider 2023.2 integrates the Qodana code quality platform. Learn how you can elevate the quality of your C# code with Qodana in this blog post. You can find more general information about Qodana here.
  • Rider’s F# support has received a number of exciting updates, starting with F# to C# in-memory references. Learn about all of the F# updates here.
  • Rider 2023.2 comes with support for the LSP API for plugin developers. Here’s a blog post about it from the IntelliJ IDEA team.
  • Rider 2023.2 introduces the Feature Trainer, a new interactive tool designed to help both new and experienced users familiarize themselves with the extensive features and workflows offered by the IDE.

New in Rider 2023.2 Build 232.8660.134 EAP 10 (Jul 21, 2023)

  • AI Assistant becomes a separate plugin.
  • Live Coding and Hot Reload support introduced for Unreal Engine.

New in Rider 2023.1.4 Build 231.9225.23 (Jul 19, 2023)

  • We fixed the issue with missing custom code style settings – they are now correctly preserved by the IDE. [IDEA-318457]
  • The Copy Reference action for files in non-Java modules works as expected and copies the path from the content root. [IDEA-316752]
  • Starting up the IDE no longer fails with the “CannotActivateException: Address already in use: bind” error. [IDEA-323836]

New in Rider 2023.2 Build 232.8660.64 EAP 9 (Jul 14, 2023)

  • Support for the primary constructors for non-record class and struct from the C# 12 Preview.
  • Support for the IAsyncDisposable interface in the “Generate Dispose Pattern” feature.
  • New inspections, quick-fixes, and Push-to-Hint mode for handling C# discards support.

New in Rider 2023.2 Build 232.8296.16 EAP 6 (Jun 26, 2023)

  • AI Assistant.
  • Customizable project headers.
  • Inspections and quick-fixes for discard handling.
  • Inlay hints for LINQ.
  • New Structure View filters and sorters.
  • Accessibility improvements.
  • Project templates for Roslyn analyzers and Source Generators.
  • ARM32 support for the remote debugger.

New in Rider 2023.1.3 Build 231.9161.46 (Jun 23, 2023)

  • Rider updater would crash with out-of-memory (OOM) errors (RIDER-91408).
  • The Go to Definition action would not work for methods in Blazor Components when using Rider 2023.1.1 (RIDER-93077).
  • Web-application targeting ASP.NET (.Net Framework 4.8) could not run locally under IIS Express (RIDER-92177).
  • The RiderLink plugin build 2023.1.0.281 failed to compile with Visual Studio 2022 v17.6 (RIDER-93789).
  • Localization errors in Simplified Chinese (RIDER-92002 and RIDER-93304).
  • The IDE would crash if Navigation was used inside the Raycast launcher app (IDEA-317346).

New in Rider 2023.2 Build 232.7754.74 EAP 5 (Jun 20, 2023)

  • Support for default parameter values in lambdas.
  • New inspections for improved control over object disposal.
  • Migration of the terminal emulator to ConPTY on Windows.
  • Group by Thread option for call tree grouping of performance snapshots.

New in Rider 2023.2 Build 232.7295.15 EAP 4 (Jun 9, 2023)

  • Improved navigation from var declarations.
  • Optimized Blueprint indexing for Unreal Engine.
  • Labels for fine-tuning run configurations in Docker Compose.
  • Pinned run configurations in the Run widget.
  • File sorting by modification time in the Solution Explorer.
  • Volar support for Vue.
  • Next.js custom documentation support.
  • CSS color modification options.
  • Improvements for working with databases.

New in Rider 2023.2 Build 232.6734.14 EAP 3 (Jun 6, 2023)

  • Improvements for working with C# raw string literals
  • Reworked hamburger menu in the main toolbar on Windows and Linux
  • Updated window controls on macOS
  • Text search in Search Everywhere
  • Light theme with light header in the new UI
  • Single-click navigation between project directories
  • GitLab integration
  • Memory snapshot analysis

New in Rider 2023.2 Build 232.6095.13 EAP 2 (May 22, 2023)

  • C# inspections and quick-fixes for common Entity Framework issues.
  • A reworked Build tool window.
  • XAML Hot Reload for MAUI.
  • Improvements for working with Source Generators.
  • The new Feature Trainer tool.
  • The option to navigate between running IDE instances by color.

New in Rider 2023.1.2 Build 231.9011.39 (May 18, 2023)

  • Rider was hanging after updating to 2023.1 (RIDER-92254).
  • The IDE would freeze when the user created a baker before including Unity.Entities in a Unity project (RIDER-92309)
  • .NET Framework projects in the .csproj format weren’t being built after upgrading to 2022.3.1 (RIDER-87113).
  • The Options and Hide buttons in the Debug window disappeared after disabling the New UI (RIDER-84418).
  • Rider was showing the VSTS Device Code Authentication dialog repeatedly and failed to get a token (RIDER-91953).
  • Hot Reload was not working for layout changes in ASP.NET Core MVC apps on macOS (RIDER-69650).
  • Language injections were interfering with the Undo action (RIDER-85801).
  • Remote debugging would not allow you to upload the debug tools (RIDER-86140).
  • Rider was sometimes unable to debug Docker Compose (RIDER-92541).
  • #r “nuget: PackageName” was not working for F# script files (RIDER-86308).
  • Unreal projects loaded from .uproject failed to show game configurations (RIDER-87087).
  • There was a problem with debugging Azure functions in an isolated worker launched under Rosetta (RIDER-92326).
  • Editor tabs would scroll very slowly (IDEA-318576).
  • The Build button had an incorrect layout in the new UI (IDEA-304472).

New in Rider 2023.2 Build 232.5150.114 EAP (May 16, 2023)

  • C# inspections for #nullable directives and NRT annotations.
  • Inlay hints for tuples, discards, and deconstruction components.
  • Find Usages Advanced.
  • Option to run Docker on the WSL.
  • Improved code completion for Unity shader includes.
  • UnrealHeaderTool code inspections fix for Unreal Engine.

New in Rider 2023.1.1 Build 231.8770.54 (Apr 27, 2023)

  • A bug causing Rider’s code inspection to incorrectly interpret null-coalescing operators, falsely claiming that the left side of the operation can never be null (RSRP-491824).
  • An error causing Rider to display the loading status symbol for unit tests that have already been run (RIDER-92123).
  • A behavior where Rider would display bogus “already in interface list” inspections for interfaces nested inside a generic class, and referencing the nested interface in child classes of the generic class (RSRP-491716).
  • Incorrect operation of the automatic ESLint configuration (RIDER-92039).
  • Issues causing some erratic behaviors in the Editor window, particularly when navigating into a file using Search Everywhere (RIDER-88940).
  • A bug causing Rider to crash Unreal Editor when opening a Blueprint (RIDER-91969).
  • A bug causing a critical failure to occur when navigating to errors detected by Rider in source code generated by a .NET source generator (RIDER-91153).
  • Schema Compare couldn’t be used with the latest SQL Server Data Tools (RIDER-92298).
  • A bug making Rider unable to rename files in solutions referencing Nerdbank.GitVersioning ( RIDER-89973).
  • The missing Cancel button in the Apply Changes window in the debugger (RIDER-90284).
  • Instances of false red code in Razor projects (RSRP-491750).
  • Additionally, Rider now supports authenticated access to images in GitHub (IDEA-316245).

New in Rider 2023.1 Build 231.8109.192 Beta (Mar 31, 2023)

  • New C# inspections to optimize your work with various types of collections.
  • More adjustable ways to introduce null checks in your C# code.
  • Support for Unity’s DOTS.
  • VCS widget for Perforce.
  • Support for Unreal Engine 5.2.
  • Unreal Engine’s Blueprint error parsing.
  • Visualizers for string variables.
  • Color and brush previews for Avalonia XAML and C# files.
  • Full IDE zoom.
  • Improvements to the New UI, including Compact Mode.
  • Database Schema Compare.
  • Fast mode running and auto-generated run configurations for Docker.
  • The Reattach to Process action.
  • New postfix templates, language injections, and quick-fixes for F#.
  • IDE Localization (Beta).
  • Structure view improvements.
  • Rename refactoring.
  • Many smaller improvements and fixes.

New in Rider 2022.3.3 Build 223.8836.53 (Mar 23, 2023)

  • We’ve resolved the issue that caused the screen to flicker in full-screen mode on macOS Ventura (JBR-4959).
  • The IDE no longer displays empty popups on macOS Ventura (JBR-5258).

New in Rider 2023.1 Build 231.7864.80 EAP 7 (Mar 6, 2023)

  • Game development:
  • We've added the following new features in this version:
  • Support for Unity DOTS.
  • The ability to debug applications on Android devices via USB.
  • Temporary run configurations for attached players.
  • Built-in UInterface live template for Unreal Engine solutions.
  • UX/UI:
  • The new Version Control widget for Perforce has been added for both the current and the new UI.
  • Debugger:
  • We implemented a set of fixes for the Blazor WASM debugging experience.
  • F# support:
  • Support for F# has been bolstered by:
  • New postfix templates match, for, and with.
  • Support for regular expressions in string literals.

New in Rider 2023.1 Build 231.7665.34 EAP 6 (Feb 24, 2023)

  • New UI improvements:
  • Vertical split for tool windows
  • Compact mode
  • Project tabs on macOS
  • Redesigned Run widget
  • Show Hidden Tabs
  • Debugger:
  • Starting with this build, whenever you debug an ASP.NET Core application with a JavaScript debugger enabled, Rider will close the corresponding browser tab the moment you stop the process.
  • Inlay hints:
  • Option to hide type conversion hints
  • Parameter name hints for xUnit attributes

New in Rider 2023.1 Build 231.7515.11 EAP 5 (Feb 19, 2023)

  • Schema Compare for connected databases, SQL Server database projects, and .dacpac files.
  • Debugger visualizers for HTML, XML, JSON, JWT, and URL-encoding.
  • New Reattach to Process action.
  • New Trigger Continuous Testing action.
  • Reformat inactive preprocessor branches in file task inside the Built in: Reformat code profile.
  • File rename refactoring.
  • Unreal Engine: Blueprint errors in Problems View.
  • Unity: localized documentation inside tooltips for Unity APIs and improved support for finding usages of C# code in Unity animations.

New in Rider 2023.1 Build 231.6890.15 EAP 4 (Feb 13, 2023)

  • Full IDE zoom.
  • Ability to debug startup code for WASM .NET apps.
  • Initial Astro support.
  • New feature for Angular.
  • Support for TypeScript in Vue template expressions.

New in Rider 2023.1 Build 231.6471.8 EAP 3 (Feb 3, 2023)

  • The Structure view tool window received improvements and fixes.
  • DockerFile run configurations are now auto-generated from properties inside .csproj and launchSettings.json files.
  • Color and brush preview for Avalonia XAML (.axaml) and C# files.
  • A preview of localization into Chinese, Korean, and Japanese is now available.

New in Rider 2022.3.2 Build 223.8617.53 (Jan 27, 2023)

  • Performance:
  • Searching in the Search Everywhere popup shouldn’t be slow anymore (IDEA-308324).
  • Code editor:
  • The Undo action works as expected in files with language injections (RIDER-85801).
  • Web development:
  • Hot reload applies layout changes in ASP.NET Core MVC applications on macOS (RIDER-69650).
  • You can again build a web application that uses a legacy project style from the classic .NET Framework with the embedded MSBuild (RIDER-87113).
  • We fixed the crash in ASP.NET Core projects (RSRP-490776).
  • Unreal Engine support:
  • The upcoming changes in UnrealHeaderTool and Blueprints from Unreal Engine 5.2 are now supported.
  • Debugger:
  • The Options and Hide buttons stay on the Debug window’s toolbar after you disable the new UI (RIDER-84418).
  • C# support:
  • We fixed the false-positive errors for BigInteger operators in .NET 7 (RSRP-490798).
  • F# support:
  • The #r “nuget: PackageName” directive in F# script files is being resolved correctly again (RIDER-86308).

New in Rider 2022.3.1 Build 223.8214.53 (Dec 21, 2022)

  • Fixed a major performance issue with the Grazie/Hunspell plugin taking up an extraordinary CPU load (RIDER-86408).
  • Fixed a critical error in our post-installation dialogue on Windows ARM64 (RIDER-83280).
  • Restored the broken SDK that prevented users from building plugins targeting Rider 2022.3 (RIDER-86051).
  • Fixed an error where users could not run published projects on Linux ARM64 (RIDER-81658).
  • Fixed an issue preventing solutions that use Central Package Management and VersionOverride from being built (RIDER-79940).
  • Fixed an error causing the IDE to display Unicode escape sequences instead of invalid characters in high-level C# identifiers in ILViewer (RIDER-85767).
  • Fixed an issue interfering with code cleanup (RIDER-86183).
  • Fixed an error preventing building a project to Docker with a debugger attached (RIDER-86227).
  • Fixed how the list of .ignore items is displayed in the Add context menu (RIDER-86492).
  • Fixed an error causing the debug session to crash after a user accesses the database context (RIDER-86350).
  • Fixed a bug that prevented the debugger from hitting breakpoints in macOS projects (RIDER-72495).
  • Fixed an error causing the debugger to crash during step over / step out (RIDER-80867). 
  • Fixed the issue preventing Rider from reopening solutions on startup (RIDER-85672).

New in Rider 2022.2.4 Build 222.4459.9 (Nov 9, 2022)

  • Fixed the CVE 2022-41032 vulnerability Microsoft recently uncovered in .NET 7.0.0-rc.1, .NET 6.0, .NET Core 3.1, and NuGet clients (NuGet.exe, NuGet.Commands, NuGet.CommandLine, and NuGet.Protocol).
  • Fixed an error that was preventing Rider from building projects that target Unreal Engine 5.1 Preview on MacOS (RIDER-83762).
  • Fixed an error causing Rider to interfere with the processing of T4 text templates in Microsoft Visual Studio (RIDER-80838).

New in Rider 2022.2.3 Build 222.4167.23 (Sep 14, 2022)

  • Resolved an issue preventing you from previewing the changes in Unity project packages version control in real time (RIDER-81011).
  • Rider’s basic functionality no longer stops working after a Perforce commit (RIDER-81036).
  • Rider doesn’t freeze after launching the Unreal Editor (RIDER-8142).
  • Fixed the bug causing Rider to re-cache solutions (in particular, Unreal Engine solutions) every time one is loaded (RIDER-79069).
  • “Reformat and cleanup” action from the Solution Explorer does not get stuck in an infinite loop anymore (RIDER-80839).
  • Fixed the behavior causing projects to build error-free in spite of Code Analysis showing multiple errors (RIDER-81534).
  • Fixed the bug causing solution folders to double for solutions loaded from GitHub (RIDER-81217).
  • Restored normal operation of Code Analysis for Unity projects (RIDER-81268).
  • Fixed a performance issue with a 57-freeze in an Event Dispatch Thread (RIDER-78896).

New in Rider 2022.2.2 Build 222.3962.23 (Aug 24, 2022)

  • An error causing Rider 2022.2 to fail to launch Unreal unit tests was fixed (RIDER-80627).
  • An error preventing the use of Perforce in a project using the preconstructed version of the Unreal Engine was fixed (RIDER-80582).
  • An error that occurred when debugging an MSTest in Rider without privilege-elevation was fixed (RIDER-78265).

New in Rider 2022.2.1 Build 222.3739.37 (Aug 11, 2022)

  • Fixed the issue that led to the inability to add or remove files after stopping a running application (RIDER-79708).
  • Fixed an error that broke Code Analysis for Unity projects (RIDER-80530).
  • Fixed the issue preventing the DPA runner from passing the stop signal to an app (RIDER-79182).

New in Rider 2022.2 Build 222.3345.139 (Aug 3, 2022)

  • Performance improvements:
  • A significant portion of the work during this release cycle was focused on various performance improvements, particularly the optimization of the startup process and the solution-wide engine.
  • For version 2022.2, we’ve migrated Rider’s Windows backend to the .NET 6 runtime. The move boosted performance by leveraging this runtime’s own optimizations and enabled us to replace NGen with the CrossGen utility. CrossGen works with the .NET 6 runtime and is cross-platform, which helps Rider start up and open solutions faster.
  • We’ve also optimized the initial project-loading stage. Solutions now load approximately 40% faster when you open them in Rider for the very first time (a process known as “cold startup”).
  • Rider’s memory usage with Solution-Wide Analysis mode turned on has been radically optimized. The improvements affect both memory traffic (number of memory allocations) and memory consumption, resulting in a 5-10x memory consumption improvement and faster Solution-Wide Analysis loading.
  • C# 11 features:
  • With our latest release we’re continuing to expand Rider’s support for the C#11 preview, starting with recognizing required members.
  • Rider is now aware of the required keyword for members inside a class, struct, or record type, and is able to provide additional support for the required keyword. There’s a required keyword in code completion, a required modifier in the “Modifiers order”, as well as all relevant compiler errors and warnings.
  • Support for checked user-defined operators is another C#11 feature that made it into this release. We’ve added relevant compiler errors and warnings and introduced a couple of new inspections and a context action. Rider’s “Unchecked/checked context is redundant” inspection has been updated to take into account checked operators when they are used in this context.
  • If you have a set of user-defined operators and some of them already have a checked version, Rider will help you propagate checked operators to the whole set. If you haven’t used checked operators in your codebase yet, but want to start adding them, a new context action called “Create matching checked operator” will help you with that.
  • Rider 2022.2 also has basic “raw” string support including compiler errors and correct parsing and color highlighting for “”” syntax, pairs of double quotes, and placeholders inside interpolated strings ({{...}} syntax).
  • Unreal Engine support:
  • Rider has been deeply integrated with Unreal Engine since the 2022.1 release. This time around, we’re bringing out a whole new set of features to enhance your game development experience: new actions, symbol servers, support for spec tests, and UX/UI improvements.
  • When you create a new module with game logic, there’s a long list of steps you need to take: add a folder, add a Build.cs file into this folder, create a class that initializes the module, and update the .uproject and Target.cs files. Rider can now automate these tasks for you with the new Add | New Unreal Module… action available in the solution view via a context menu.
  • Another action that will help you streamline your work is Add | New Unreal Plugin. It enables you to create different types of plugins right from Rider by generating all the necessary files in one go.
  • When debugging, the library symbols may not always be available on your local machine. In this case, you can use symbol servers. In Rider on Windows, you can now configure the debugger to use the symbol server of your choice.
  • Early preview of MAUI support:
  • Rider 2022.2 contains an early preview of our .NET Multi-platform App UI (.NET MAUI) support. In this release we support projects that target the Android and iOS platforms. You can use run configurations to run and debug your project as well as to deploy your application to a target device.
  • macOS, Mac Catalyst, Blazor Hybrid, and WinUI aren’t fully supported yet.
  • Default settings for window layout:
  • When you’re working on more than one solution in Rider, setting up your workspace all over again for each new project can be a hassle. That’s why we’ve implemented a way to apply the same window layout settings to all of the solutions you work on.
  • For example, if you move a tool window to the right, that’s where it will be for all of your solutions. This behavior will be the default if you’re new to Rider. Otherwise, you can enable it in the main menu by selecting Windows | Layout Settings | Use the Same Layout for All Projects.
  • Other release highlights:
  • A new toolbar is available for Unity projects, and the connection status is now shown in the toolbar instead of the status bar.
  • It’s now possible to change the width of the Run/Debug widget on the main toolbar.
  • For macOS, we’ve introduced the ability to organize your working space by merging all opened project windows into one, turning each window into its own tab.
  • Solution Explorer has been reworked to include the Safe Delete refactoring on the project level as well as better support for solution filters.
  • Rider now comes with dotMemory, our memory profiling tool, built in. Check out this blog article to learn more.
  • We’ve added a coverage summary indicator to the editor to make it easier for you to navigate through the highlighting produced by the dotCover plugin.
  • dotTrace profiler can now attach to and detach from running Unity processes – no need to restart the Unity Editor.
  • We’ve extended support for Vue3 and Angular standalone components, directives, and pipes marked as standalone: true.
  • Starting with v2022.2, the Parameter Info popup for F# supports curried applications and highlights the correct method overloads.
  • We’ve introduced two new database object resolution modes: Playground and Script.

New in Rider 2022.1.2 Build 221.5787.36 (Jun 3, 2022)

  • We fixed the Windows Authentication for the SQL Server (DBE-15456).
  • We fixed the metadata for the Unity plugin. The plugin’s DLL no longer returns errors (RIDER-76619).

New in Rider 2022.2 Build 222.2680.9 EAP 2 (Jun 3, 2022)

  • We've redesigned the Solution Configuration feature to make it easier to use, and we're eager to hear how it works for you. Solution configurations are now shown on the toolbar by default for Unreal Engine projects.
  • We've improved MAUI support.

New in Rider 2022.1.1 Build 221.5591.20 (Apr 29, 2022)

  • Fixed the JetBrains Runtime crash (DEXP-667909).
  • Fixed the issue that broke the Docker debug (RIDER-76599).
  • Fixed the issue that prevented the Azure functions debug from working properly (RIDER-76273).
  • Fixed the Code Vision context menu (RIDER-76781) and the problem that prevented the user from hiding the Code Vision from the editor completely (RIDER-76596).
  • Fixed the Stack Trace Explorer that had difficulty working with multitarget projects (RSRP-488300).
  • Fixed an error that emerged when the test method’s name is the same as the value of [TestName] attribute (RSRP-488226).
  • Fixed the inconsistency between the states of the unit test session and tests generated with [DynamicData] attribute (RSRP-488356).

New in Rider 2021.3.3 Build 213.6775.4 (Jan 31, 2022)

  • We’ve fixed the issue with NuGet feeds: they should no longer be missing (RIDER-72647).
  • We’ve fixed the ordering in F# projects (RIDER-72693).
  • We’ve fixed the problem that was causing the test coverage to hang (RIDER-72256).
  • We’ve fixed the empty tooltips and quickdocs in F# files (RIDER-71127).
  • We’ve fixed the issue with stopping on breakpoints while debugging (RIDER-71495).
  • We’ve fixed renaming controls in WinForms designer (RIDER-67564).
  • We’ve fixed the issue with navigating to test method that was broken for tests with the [DisplayName] attribute (RSRP-477725).
  • We’ve added support for Xcode 13.2.1 (RIDER-73201).

New in Rider 2021.3.2 Build 213.6461.51 (Dec 24, 2021)

  • We’ve fixed the issue that caused a failure when publishing a Blazor WebAssembly project to a folder (RIDER-71884).
  • We’ve fixed the functionality for copying text from the debug console with Ctrl+C (RIDER-70668)
  • We’ve fixed the slowdowns and crashes caused by an issue in code analysis (RIDER-71868, RSRP-487310).
  • We’ve fixed the shortcut issue in the NuGet tool window (RIDER-72074).
  • We’ve fixed the issue shortcuts that were working unreliably in unit testing (RIDER-71771).
  • We’ve fixed the empty tooltips in F# (RIDER-63985).
  • We’ve added support for DevExpress 21.2 (RIDER-70552).

New in Rider 2021.3 Build 213.5744.293 (Dec 8, 2021)

  • Support for .NET 6, including Hot Reload:
  • Now you can enjoy official support for .NET 6 SDK in Rider. It includes project templates, the latest target frameworks, the latest NuGet API, Blazor WebAssembly debugging, creating/running/debugging projects targeting the new SDK, ASP.NET scaffolding for .NET 6 projects, and Hot Reload. In our previous blog posts, we covered how you can work with Hot Reload in Rider if you are targeting .NET 6 and how it actually works.
  • Redesigned main toolbar with a new Run/Debug widget:
  • We’ve completely redesigned the main toolbar. The old main toolbar had problems that we wanted to eliminate:
  • There were too many icons, most of which were hardly ever used.
  • The VCS and the navigation functionality were not discoverable.
  • It was not possible to control multiple run configurations.
  • With the new design, we’ve tried to give our users a cleaner, more functional toolbar. It includes a new Run/Debug widget, navigation buttons, a VCS widget, a large Search Everywhere field, a Solution Configuration widget for managing solution-related configurations, and more. You can learn about the revamped main toolbar and how to use its features in this blog post.
  • Note: if you had Rider installed before this release, you won’t see the new toolbar by default, as we didn’t want to disrupt your user experience. You can give the new toolbar a try by enabling it under View | Appearance | Toolbar.
  • Updated debugging experience:
  • A new UI has come to the Debug tool window! Now it has three tabs: Threads & Variables, Console, and Debug Output. We removed the toolbar on the left and transferred the icons to either the top toolbar or the context menu.
  • We also have good news for UWP developers: you can now start your UWP project with the debugger attached. You no longer need to run the project first and then manually attach the debugger to the running process.
  • Another big update is that you can now debug both .NET (Core) and .NET Framework apps in local Windows Docker containers.
  • New Problems View tool window:
  • We’ve introduced the Problems View tool window (the Problems tab in the Rider UI) to give you an easy way to see warnings and errors for the current file, or whole solution, and problems with missing tooling and broken environment configurations.
  • The tool window has three tabs:
  • Current file – all of the errors, warnings, suggestions, and hints that Rider code analysis found in the file you are currently working on
  • Toolset, Environment – all of the diagnostics and messages related to the solution load activities, NuGet restore processes, and so on
  • All Solution Files – all the errors that Solution Wide Error Analysis found in the whole solution.
  • Updates to code analysis:
  • More C# 10 features:
  • Rider continues to add more C# 10 features. In this release, we’ve added support for file-scoped namespaces, global usings, the CallerArgumentExpression attribute, the “interpolated string handlers” concept, and C# 10 lambdas. You can learn how Rider can make it easy to adopt them in your codebase in our series about the new C# 10 features.
  • Nullable reference types:
  • Rider has two new quick-fixes, Replace with JetBrains.Annotations attributes and Remove nullable annotations without ‘#nullable’ context. These help you get rid of NRT syntax when you copy code samples from other resources but don’t have NRT enabled in your solution. There are also new quick-fixes for mismatches between type arguments and their nullability constraints, as well as for correcting annotations on parameters with nullable default values in a file, project, or whole solution.
  • Improved support for SQL language injections:
  • We now support many common cases where you write SQL code right inside of C# code. For instance, SQL query strings are correctly resolved for string.Format methods, string interpolations, and simple string concatenations.
  • Updates for Unity:
  • This release brings major updates to Rider’s support for Assembly Definition Files:
  • You can use Ctrl+Click to navigate to a reference; find usages of assembly definitions across the whole project, even in referenced packages; rename assembly definitions; and get completion when adding new references.
  • Rider will work with GUID based references, displaying a helpful hint with the target assembly definition’s name and Alt+Enter actions to convert between named and GUID-based references.
  • Rider will now highlight unmet “define constraints” in Assembly Definition Files. This makes it easy to see why an assembly has been excluded.
  • Setting up version defines has also gotten easier, with completion for package names and an inlay hint for the currently installed version.
  • Other highlights include:
  • Support for Apple silicon processors: no more x64 to ARM64 translation! Rider is now much faster on Apple chips.
  • Xamarin: in the Plist editor, we’ve implemented support for standard Xcode schemes. They help Rider provide understandable names for keys, value validation according to key type, and a list of possible keys when you add a new one to the Plist. These work on both macOS and Windows.
  • The XAML Preview now works for applications that target the .NET 6, .NET 5, and .NET Core 3.x SDKs. You can preview the results of any change you make in XAML code directly in Rider.
  • Rider can generate Binding Redirects for NuGet packages in .NET Framework projects. If Binding Redirects are needed in your project, Rider will add them to the App.config or Web.config file.
  • Rider now officially supports F# 6. There are powerful updates for the Introduce Variable refactoring, and using F# functions recursively is now easier, as you don’t have to go back and manually add rec to the containing function.
  • We’ve introduced the Reformat and Cleanup on Save setting. This feature allows you to reformat and tidy up whenever you explicitly invoke Save or Save All in the IDE. We hope it helps you keep your code nice and neat and saves you the trouble doing it manually.
  • We’ve introduced the new Bookmarks tool window that will replace a similar instance – Favorites.

New in Rider 2021.2.2 Build 212.5284.64 (Oct 14, 2021)

  • ReSharper:
  • We’ve brought back the compatibility of JetBrains.ReSharper.GlobalTools package with .NET Core 3.1 (RSRP-485977).
  • We’ve fixed a number of issues in support for C# 10 constant interpolated strings.
  • We’ve fixed the false positive errors in Blazor projects on built-in attributes (RSRP-485551).
  • We’ve fixed the issue that caused ReSharper to use the wrong version of the MSBuild (RSRP-485214).
  • We’ve fixed yet another case of the ? operator being treated incorrectly (RSRP-485691).
  • For the whole list of fixes, please see our bug tracker.
  • dotCover:
  • We’ve fixed the issue that prevented the GetSnapshotAndKillChildren command from being finished correctly (DCVR-10774).
  • dotTrace:
  • We’ve fixed the issue that caused the controller buttons to be disabled while the snapshot is being flushed in Tracing and Line-by-Line modes (PROF-1178).
  • Rider:
  • We’ve fixed a number of issues with the built-in console, including broken Console.Clear, wrong display of background color, and more (RIDER-66804).
  • We’ve fixed the Alt+Shift+R shortcut for rename refactoring (RIDER-66581).
  • We’ve fixed the issue that prevented Rider from reopening multiple projects on startup (RIDER-66612).
  • We’ve fixed the stack overflow issue that occurred during the indexing (RIDER-66596).
  • We’ve fixed the false positive errors in Blazor projects on built-in attributes (RIDER-67011).

New in Rider 2021.2.1 Build 212.5080.71 (Aug 27, 2021)

  • No more errors on an Average() call being ambiguous between Nullable and Nullable (RSRP-484898), and no more ‘The type xxx is defined in an assembly that is not referenced…‘ error for Unity/Mono projects (RSRP-485467).
  • ASP.NET Core routes no longer pollute the search result of Search Everywhere (RSRP-485344).
  • We’ve fixed the root cause of slow nullable code analysis in some cases.

New in Rider 2021.2 Build 212.4746.113 (Aug 18, 2021)

  • Support for ASP.​NET Core Endpoints:
  • We introduced the new Endpoints tool window to help you explore and navigate to any ASP.​NET Core endpoint in your project that is registered or annotated with [Route], [Http{Method}], or [AcceptVerbs] attributes. You can inspect endpoint documentation, jump to the source of the controller that implements an endpoint, or find usages to see where it is registered.
  • In the code editor, you will get first-class support as well! When you use HttpClient, code completion will suggest all URIs that can be resolved to actions in controllers annotated with [Route], [Http{Method}], or [AcceptVerbs] attributes. Renaming an attribute route in a controller affects its usages in URIs, and you can even rename a route directly from the URI string.
  • You can also use the HTTP Client tab to create and submit requests to your application. This is useful for testing APIs. Learn more in our blog post A Better Way To Discover APIs With The New Endpoints Window.
  • Blazor WebAssembly Debugging:
  • The long-awaited client-side debugging for Blazor WebAssembly has come to Rider! Currently, it works for .NET 5.0 and .NET Core 3.1 applications. To get started, follow the official Microsoft guide to set up WASM debugging. Then just start debugging your applications as usual.
  • When starting a debugging session, the debugger launches and attaches to an instance of Chrome or Edge, including Edge on Ubuntu. From there, you can switch between the web UI and the debugger. Read more about this in our blog post Blazor debugging improvements in Rider 2021.2.
  • Code Analysis:
  • If you still use temporary variables to swap variable values, Rider 2021.2 will help you modernize your code with the new Swap via deconstruction quick-fix!
  • New useful inspections that come with the corresponding quick-fixes: Replace empty array creation with Array.Empty, Replace new EventArgs() with EventArgs.Empty, and Replace Type[0] with Type.EmptyTypes.
  • Rider respects the generated_code property from your .editorconfig file, allowing you to specify which files to ignore in its code analysis.
  • Code Analysis is getting a couple of performance improvements for the Find similar issues feature and for large and complex switch statements and switch expressions.
  • Nullable Reference Types:
  • Rider now indicates suppressions (!) that are no longer needed and that can be safely removed.
  • A new context action lets you search for all nullable warning suppressions in scope. From the Find Results tool window, you can then re-evaluate whether the suppressions are needed or not.
  • We’ve introduced a new refactoring to change nullability, which will update nullability annotations and suggest propagating the changes throughout your codebase.
  • Several new inspections with corresponding quick-fixes are available when you’re using JetBrains.Annotations attributes and nullable reference types are enabled.
  • Rider adds new inspections and quick-fixes to help you with using compiler-supported annotations such as [DisallowNull], [AllowNull], [MaybeNull], and [NotNull].
  • Source Generators Support:
  • Many of the features available for manually-written code files are also available for source-generated files. For generated code, warnings and errors are displayed in the editor and on the marker bar. Refactorings, like Rename and Change Signature, can now be triggered from source-generated files.
  • You can now use Find Usages, search for inheritors, and navigate from generated code to manually written code with Ctrl+Click and Navigate To. Semantic highlighting is enabled so that class members like events, fields, and properties are highlighted correctly. All inlay hints are shown where appropriate. ​​Also, Rider now supports code generated by source generators in VB​.​​NET.
  • Updates for Game Development:
  • Rider 2021.2 continues with its mission to be a great game development IDE, with a lot of treats for developers who are using Unity. Just to mention a few:
  • Rider’s smart integration with the Unity editor will now check if any scenes are open and unsaved before you commit code. You can be sure that everything is saved before committing!
  • Rider has long shown a link to Unity’s documentation in the tooltip for a Unity class or method, but now you can use the External Documentation action and shortcut to jump straight to the docs without showing the tooltip first.
  • Rider can now debug local UWP players by correctly asking Windows to allow incoming connections to the process being debugged.
  • This release improves the experience of debugging IL2CPP-based players, by automatically disabling “break on unhandledexception” when it connects to a IL2CPP player.
  • There are also breakthrough improvements to our early-preview Unreal Engine support – it now works on Mac, supports Unreal Engine 5, and is able to open .uproject files. Check out Game Zone in Rider 2021.2 for other improvements.
  • Import Settings from other IDEs:
  • For the convenience of first-time Rider users, we’ve come up with a new Import Settings feature. If you’ve never installed or used Rider before, the Welcome wizard now lets you import settings from other IDEs such as Visual Studio, Visual Studio for Mac, or Visual Studio Code. In addition to this, Rider will also recognize settings from ReSharper. Read more about how importing settings from other IDEs works. We’d love to hear from you about your experience with this new feature.
  • Code Cleanup:
  • In Rider 2021.2, we’ve merged the Reformat File and Code Cleanup dialogs into one unified view that allows you to perform both steps at the same time. Cleanup profiles will also preview which actions will be executed, and you can easily switch to the profile editing mode with a button.
  • There is also the option to reformat/cleanup only uncommitted changes in the current file. In the commit dialog, you can now enable automatic code cleanup for your changes with the profile of your choice.
  • Among other highlights:
  • There are some improvements for version control. We’ve added a search field to the Local History dialog to help you quickly get to the necessary text in your Local History revisions. Also, it is now possible to enable Git commit signing with GPG via Preferences/Settings | Version Control | Git.
  • In the editor, we’ve implemented structural removal of code – select and delete code with any kind of structural selection (such as structural navigation, extend/shrink selection, or rearrange code) and let Rider perform the remaining structural modifications. You can remove commas and colons for method call arguments, parentheses in attribute arguments, or braces for empty object initializers.
  • It is now easier to drag a tool window to the desired place within the main IDE window or in a separate window. You can drag it by clicking and holding the tool window name bar and dropping it in any highlighted area.
  • There’s a number of updates for Xamarin users. We’ve added support to generate .aab (Android App Bundle) in addition to .apk files, which will soon be the only way to upload your apps to the Google Play Store. XCAssets can now be created and edited for imageset, appiconset, and colorset right inside of Rider.
  • For developers using F#, we’ve introduced postfix template for let and some new actions for rearranging the code, pattern deconstruction for F# tuples and union cases, optimizing imports, and more.
  • Apple Silicon support in Rider: we have an early preview version with full native M1 chip support. Check out this page for more information.
  • Do you practice Behavior Driven Development (BDD) in .NET? With the new SpecFlow plugin for Rider, you can now enjoy a much smoother experience when embedding automated SpecFlow test cases into their projects. Read more about how BDD and Rider help you write better, more maintainable code through the use of automated tests.

New in Rider 2021.1.5 Build 211.7628.61 (Jul 25, 2021)

  • In Rider 2021.1.5, we’ve fixed a significant performance degradation. We’ve also fixed an issue with the F# type providers loader that was causing Rider not to start in some cases, and an issue causing changes in an F# file to be ignored when other files in the project were analyzed.

New in Rider 2021.1.4 Build 211.7628.50 (Jul 14, 2021)

  • We’ve fixed the vertical indent lines in the code editor (RIDER-62679).
  • We’ve fixed the update notifications from plugins that were disabled (IDEA-267878).
  • We’ve fixed the issue that caused unrelated results to be shown in Find in files (RIDER-63634).
  • For the full list of issues, please refer to our bug tracker.

New in Rider 2021.1.3 Build 211.7442.29 (May 26, 2021)

  • Fixed the issue that led to resetting the custom color scheme (RIDER-61653).
  • Fixed the incorrect behavior of the focus on macOS Big Sur (RIDER-62393).
  • Fixed the stepping when debugging a .NET Core project (RIDER-62227).
  • Fixed the “Wrong client specification” issue in Perforce support (RIDER-61551).
  • Fixed Search Everywhere for databases (RIDER-61397).
  • Fixed several issues in web development (RIDER-62290).

New in Rider 2021.1.2 Build 211.7142.19 (Apr 25, 2021)

  • We’ve fixed a number of issues in web development, such as false errors in .xaml files, Locate and Select in Solution View issues, and others.
  • We’ve fixed the issue that broke the Find in Files feature (RIDER-61392).
  • We’ve fixed the issue that caused Run/Debug Configuration to disappear (RIDER-60924).
  • We’ve fixed the issue with controls in WinForms Toolbox (RIDER-60335).
  • We’ve fixed the issue in the Show Neighbours feature in project diagrams (RIDER-60525).
  • We’ve brought back the database diagrams (RIDER-61248).

New in Rider 2021.1.1 Build 211.6693.127 (Apr 12, 2021)

  • Update to Docker Support:
  • Adding Docker support to a project in Rider is now easier – you can generate the Dockerfile while creating a new project. Just select Docker Support in the New project dialog. If you want to add a Dockerfile to an existing project, use Add | Docker Support in the context menu for a project in the Solution Explorer tool window.
  • Rider can also run Dockerfiles generated by Visual Studio with no additional changes required from you.
  • Scaffolding for ASP.NET:
  • There’s good news for developers who work with ASP.NET MVC, ASP.NET Web API, or Razor Pages: we’ve added a scaffolding mechanism for ASP.NET Core projects. Rider supports scaffolding Areas, Controllers, Razor Pages, Views, and Identity. It even generates boilerplate source code for full CRUD operations to use Entity Framework.
  • C# support:
  • We’ve put a lot of effort into better supporting patterns and records. As a result, the Merge into pattern inspection can now be used with many more code patterns. Additionally, a set of new inspections and corresponding quick-fixes are available to help you work with records. The Extract interface and Extract superclass refactorings now work with record declarations, as well.
  • In addition to that, we’ve introduced:
  • A new inspection, Inline temporary variable.
  • The Rename refactoring for named tuples. Named tuples have been with us since C# 7, and finally, you can call this well-known refactoring for them as well.
  • For those who are keen to use cutting-edge technologies, we’ve taken some first steps toward offering support for C# 10.0 and taught Rider to work with the Constant string interpolation feature.
  • Debugger:
  • You can now attach to a .NET process right from the Welcome screen! No need to open a solution with the source code first. Just select the Attach to process tab on the Welcome screen, choose the .NET process you need from the list, and Rider will begin debugging it.
  • The second big feature we’ve added to the debugger is interactive debugger hints. Hints in the editor not only show you what’s going on but also allow you to intervene in and interact with the debugger process. You can input raw data or use other values with the help of autocompletion.
  • Pull Requests improvements:
  • This release brings a huge set of improvements for working with pull requests:
  • The Pull Requests (PR) view now features a drop-down list with all the available repositories for the current project.
  • PR creation is now straightforward – just click the “+” icon or go to Git | GitHub | Create Pull Request.
  • Support for PR templates is also here. Add a pull_request_template.md file with the PR description to your project, and every time you create a PR, this description will appear in it.
  • Other goodies:
  • We have lots more in this release. Check out the long list below!
  • Web development:
  • Apart from the scaffolding feature:
  • We’ve introduced support for route templates. Rider now provides code completion, structural navigation, inspections, and quick-fixes for them.
  • The option to delete existing files in a folder before publishing is now available.
  • MDN documentation is now bundled with Rider.
  • Preview HTML files quickly with the new built-in browser preview.
  • Unity support:
  • Rider can show you where Unity is using your code inside animation assets, showing usages of properties and methods as animation callbacks.
  • Code completion and validation are now available for Unity’s animation state values.
  • The new release adds menu items that show the methods that are called in the hot path back up to an Update method, or that trace the outgoing calls to finally reach a known expensive Unity API.
  • You can debug SerializedProperty instances.
  • Rider has extended its Unity-based unit testing support to include code coverage for play mode tests.
  • Godot:
  • Our Godot Support for Rider plugin now supports running NUnit unit tests directly in the game process to ensure everything works as expected.
  • UI/UX:
  • Rider now saves the Solution Explorer’s state, including opened nodes, when the IDE is closed and later re-opened.
  • We’ve improved our XAML Preview tool.
  • When there are several vertically split editor tabs open, you can now double-click on each one to maximize the editor window for it.
  • We’ve reworked the folder selection dialogs on Windows. Now it will only show you folders that you are able to select.
  • Toolbox manager for the Windows Forms designer has been completely redesigned.
  • On Windows, you can now access your recent projects by right-clicking the Rider icon on the taskbar or on the Start menu.
  • Editor:
  • Syntax highlighting is now available in the Quick Documentation window, where it will provide the same highlighting you see in the code editor.
  • You can fine-tune the weight of your main and bold font styles in Preferences / Settings | Editor | Fonts.
  • Code styles:
  • We’ve added a couple of new formatting settings.
  • We’ve added a new Reindent only action for Format Selection.
  • We’ve improved how Rider reads settings for naming rules from EditorConfig and how it writes user-defined naming rules to EditorConfig.
  • F# support:
  • We’ve added the new Inline Variable refactoring for local let bindings.
  • Rider can now calculate an allowed language level based on the project and compiler used in a build, and it can suggest improvements to make your F# code more up-to-date.
  • To Interpolated String, a new analyzer and quick-fix, can help convert a printf-style format string to an F# 5 interpolated string.
  • Last but not least:
  • We’ve implemented NuGet Smart Restore on build.
  • Rider now supports building in parallel on recent versions of Mono.

New in Rider 2020.3.4 Build 203.7148.23 (Mar 18, 2021)

  • This release of Rider is about addressing security threats, namely the recent attempts to attack security researchers by sending them Visual Studio projects containing malicious code. When opening such a project, Rider will ask MSBuild to evaluate it and build an object model that Rider uses to understand the structure and dependencies of the project. Evaluating the project file may involve executing build steps, and this can result in the execution of arbitrary code. We’ve introduced the trusted projects feature to mitigate these risks.

New in Rider 2020.3.3 Build 203.7148.23 (Feb 23, 2021)

  • The overall debugger experience is as smooth and fast as it was in the 2020.2 releases, including launching the debugger, hitting breakpoints/conditional breakpoints, and evaluating values (RIDER-56637 and RIDER-56503).
  • We fixed a couple of crashes in the Immediate Window (RIDER-55760 and RIDER-55993).
  • We fixed several issues in debugging executable files generated by .NET Core such as AppHost (RIDER-55626).
  • We fixed publishing for platform-specific .NET 5 projects, e.g. Windows Forms or WPF (RIDER-56228).
  • We eliminated errors in handling partial methods with generics (RSRP-482829) and one more StackOverflow exception (RSRP-482801).
  • We fixed an issue causing the debugging of the xUnit unit tests to be painfully slow (RIDER-56587).
  • No more false positive ‘not found’ highlighting on resources from MergedDictionaries in Xamarin.Forms (RSRP-482599).
  • Dragging the horizontal scrollbar with the mouse no longer selects cells in the Localization Manager table (RIDER-47374).
  • The File Header page in the Rider Preference/Settings can now load and show a template that was saved in ReSharper (RIDER-55423).
  • You can disable the Burst-related metric in Code Vision (a pull request to the Unity plugin repo).

New in Rider 2020.3.2 Build 203.6682.21 (Dec 30, 2020)

  • Last week we published Rider 2020.3.1, which fixed several hot issues from the 2020.3 release. Unfortunately, we re-introduced the RIDER-54983 issue that affected all the icons from the plugins. The icons couldn’t be displayed in the code editor, including icons in the code completion popup, on the left margin, in Code Vision, etc.
  • This is why we’re releasing the hotfix Rider 2020.3.2 to resolve that issue. You will get an update notification shortly in Rider or in the Toolbox App.

New in Rider 2020.3.1 Build 203.6682.13 (Dec 24, 2020)

  • Fixed the issue with pausing Unity at the breakpoint (RIDER-55475).
  • Fixed the debugging of .NET Framework 2.0 and 3.5 applications (RIDER-55382).
  • Fixed starting an ASP.NET Core 5.0 application in IIS Express (RIDER-54274).
  • Fixed installing and upgrading NuGet packages (RIDER-55348).
  • Fixed opening the Settings for the New Projects window (RIDER-55258).

New in Rider 2020.2.4 Build 202.7660.16 (Oct 2, 2020)

  • Rider:
  • Fixed launching iOS apps on Xcode 12 simulators (RIDER-50673).
  • ReSharper:
  • Fixed restoring unit test sessions with continuous testing: they now persist through solution reopening (RSRP-481297).
  • dotTrace:
  • Fixed the ‘ETW collector internal error’ in Timeline profiling (DTRC-26888).

New in Rider 2020.2.3 Build 202.7319.2 (Sep 18, 2020)

  • Breakpoint icons no longer disappear from the code editor (RIDER-48535).
  • There are a few fixes in F# support related to Import missing references and the presentation of F# Unions in the debugger (RIDER-50807, RIDER-50693, RIDER-49900).
  • We’ve fixed the authentication issue when invoking remote operations in GitHub (IDEA-248658).

New in Rider 2020.2.2 Build 202.6948.24 (Sep 11, 2020)

  • Fixed cases of slowdown in building the project due to NuGet package restore (RIDER-49125).
  • Fixed an unmanaged memory leak that led to the growth of the committed memory of dotnet.exe (RIDER-49370).
  • Fixed the missing NUnit tests (RIDER-49695).
  • Fixed the debugger so that it can now be attached to remote processes (RIDER-49838).
  • Fixed the compound build/debug configuration with ‘.NET Launch Settings Profile (ASP.NET Core)’ (RIDER-49285).
  • Fixed the growing memory and freezes when working with Unreal Engine (RIDER-45872).
  • Fixed the ‘Del’ button. It now works as Delete and not as Backspace (RIDER-46520).
  • Updated a message to terminate the hanging test runner process: you now have an option to always terminate the behavior the first time you’re notified (RIDER-49584).
  • A list of Unity fixes is available on GitHub.

New in Rider 2020.2.1 Build 202.6397.268 (Aug 23, 2020)

  • NuGet:
  • We’ve fixed the bug that caused all NuGet packages to be restored unnecessarily before building the project (RIDER-49125).
  • Unit testing:
  • NUnit2 tests are no longer left in an Inconclusive state with System.NullReferenceException (RSRP-480840).
  • The option to run NUnit tests from a specified folder now works correctly (RIDER-49367).
  • The appsettings.json file is read correctly when running xUnit tests (RIDER-49177).
  • The Environment.CurrentDirectory setting for NUnit tests has been set to ‘Test assembly’s folder’ by default.
  • A variety of other requests has been fixed – please refer to this bug tracker query for more information.
  • Unity:
  • Resolving INTERNAL_DATA macros and related functions has been improved (RIDER-48368).
  • The behavior of the setting for suppressing errors in shaders has been updated: it now hides all resolve problems (RIDER-49123).
  • We’ve also turned off errors from .shader files in the ‘Errors In Solution’ view.

New in Rider 2020.1.4 Build 201.8538.1 (Jul 9, 2020)

  • Rider 2020.1.4 has a couple of fixes in addition to the C# 8 update from ReSharper:
  • No more indefinite "waiting for intention actions…" message after calling the Alt+Enter menu (RIDER-44548).
  • Rider can successfully connect to MS SQL Server (DBE-10839).

New in Rider 2020.1.3 Build 201.7846.1 (May 19, 2020)

  • The code editor no longer auto-scrolls when you type (RIDER-44278).
  • Nodes in the unit test sessions tree are updated correctly after the session tree is expanded (RIDER-44326).
  • A couple of fixes in the support for nullable reference types (RSRP-478846, RSRP-477755).
  • Code assistance in F# script files (.fsx) works again on macOS and Linux (RIDER-42925).
  • The scrolling and selection issue for the Local History diff is finally fixed for partial classes, as well (RIDER-42981).

New in Rider 2020.1.2 Build 201.7223.10 (May 8, 2020)

  • We’ve eliminated the performance issues in the Local History diff view, as well as the problems with scrolling and selection: RIDER-42981.
  • We’ve gotten rid of several false positives in C# code analysis (see ReSharper notes above).
  • The Azure Tools plugin has been updated to fix broken Azure run configurations: https://github.com/JetBrains/azure-tools-for-intellij/issues/291.
  • Unit test coverage sessions on macOS are no longer extremely slow and they no longer get stuck: RIDER-41750.
  • As usual, we’ve made several fixes and improvements to Unity support:
  • We implemented more fixes related to displaying XML documentation for Mono BCL (Base Class Library): RIDER-11155.
  • We fixed the Android plugin, which broke the “Unity Explorer” view in the release build: RIDER-43038.
  • There is a fix for a hang during “constructing components” due to excessive FileSystemWatcher initialization.
  • We improved the presentation of assets in Find Usages results.
  • We improved the presentation of the Packages folder in certain scenarios.
  • As always, you can find more details here.

New in Rider 2020.1 Build 201.6668.197 (Apr 17, 2020)

  • The backend runs on .NET Core runtime:
  • Finally, the backend runs on .NET Core runtime by default on macOS and Linux, instead of the Mono runtime. Moving to .NET Core runtime delivers noticeable performance improvements, a lower memory footprint, and multithreaded NuGet restore.
  • This is important for developers using Rider on macOS and Linux, but it is also good news for developers on Windows because bringing it to Windows is the next big step we’re going to take.
  • Now let’s have a look at the other impressive features and improvements in this first major release of the year.
  • Xamarin hot reload:
  • Now Rider automatically applies changes made in Xamarin Forms XAML to the application under debugging on a device or a simulator, without rebuilding and redeploying the whole application.
  • Dynamic Program Analysis:
  • Every time you run your project in Rider, Dynamic Program Analysis (DPA) starts collecting memory allocation data. Once you close the application, DPA will show you a list of detected problems: closures, and allocations to large and small object heaps. No need to start any “profiling sessions” and get snapshots – just work as usual and all the data will be collected in the background, with almost zero overhead.
  • Dataflow analysis of integer values:
  • Thanks to ReSharper, ​this version of Rider comes with a new type of analysis that tracks how the values of all int local variables change, and it verifies the correctness of all common operations on such variables to detect unnecessary or possibly erroneous pieces of code.
  • Deferred asset indexing for Unity projects:
  • We’ve made significant improvements in the memory usage and speed of asset indexing. Rider will now index all of your code before looking at your assets, meaning that all productivity features, such as code completion, highlighting, and inspections, are available for use sooner than before. And this is just one thing from the heap of improvements Rider Unity team has delivered in this release, which we will mention a bit later.
  • Even more features and improvements:
  • If the above is not enough to call this release feature-rich, perhaps these additional goodies will tip the scales:
  • C# code analysis reports compilation warnings related to nullable reference types and provides quick-fixes for most of them.
  • Now the code completion popup displays much faster after you begin typing, especially in large solutions.
  • We have completely reworked the UI for the Debug tool window to make it as clean and uncluttered as possible. The tabs layout is simplified, as all tabs are now on one single level, and we’ve combined the Threads and Frames views.
  • The debugger engine now supports detaching from a process initially started under the debugger without terminating the app, supports the .NET Core x86 runtime, and Smart Step Into is enabled by default for the Step Into action.
  • As already mentioned, there are a lot of other improvements in Unity support: Asset indexing understands usages of your code in Nested and Variant prefabs, unit testing discovery now works better for Unity projects, and code completion no longer suggests Boo.Lang.List or System.Diagnostics.Debug, just to name a few.
  • If our TFS client is selected in Settings/Preferences, enabling Version Control Integration now works for TFS workspaces locally created with Visual Studio.
  • For Unit Testing, we’ve tweaked the toolbars on Unit Testing windows and added new advanced Group by functionality, new filtering of unit tests by the target framework, and export/import for Unit Test Sessions.
  • A new non-modal popup where you can change the editor’s highlighting levels.
  • Extract Class refactoring.
  • Coverage Filters for the unit test coverage results.
  • Two new folders in the Solution Explorer: Implicit references and MSBuild import targets.
  • Support for WIX (Windows Installer XML Toolset) projects.
  • Tons of improvements and fixes in F# support to help you in your daily routine: new inspections and quick-fixes, a new “Send project references to F# Interactive” action, the evaluation tooltip on mouseover works for more expressions when you are debugging, and more.
  • A new Cancel build action.

New in Rider 2018.3.3 Build 183.5619.41 (Feb 11, 2019)

  • Fix for total IDE freeze if SWEA is enabled (RIDER-24120).
  • Updated plugin for Unity Editor to correctly recognize Rider installed via Toolbox App on macOS (RIDER-24173).
  • Fix to stop reindexing files on reopening a solution in Rider (RIDER-22652).

New in Rider 2018.3.2 Build 183.5619.15 (Feb 7, 2019)

  • In this update, we’ve fixed:
  • A heap of issues in the debugger (RIDER-23160, RIDER-23025, RIDER-23301, RIDER-21844, RIDER-23509, RIDER-23247, RIDER-22816).
  • Several issues in the Xamarin support (RIDER-20304, RIDER-23180, RIDER-23288, RIDER-7726).
  • More than a dozen issues in the Unity support (RIDER-23086, RIDER-22816, RIDER-23429, RIDER-22761, the list on GitHub).
  • Auto-detection of custom naming rules can be now disabled globally for all solutions (RIDER-23602).
  • The “SIGSEGV” error when running Unit Tests on the Mono runtime (RIDER-22653).
  • The issue in a WPF project when the MSBuild.Sdk.Extras and the SDK style csproj are used (RIDER-23272).

New in Rider 2018.3.1 Build 183.5253.26 (Jan 10, 2019)

  • Fixes for:
  • Several issues in the debugger: RIDER-23087, RIDER-22932, RIDER-22770, RIDER-22887, and RIDER-22873.
  • Broken NuGet window after searching for “mongo” text (RIDER-22927).
  • Endless “Retrieving properties…” progress bar for Project Properties (RIDER-22924).
  • Inability to activate the dotTrace plugin via the License Server (RIDER-22876).
  • The “Failed to get the list of simulators” error on getting a list of iOS simulators (RIDER-22878).
  • The issue where a .jar setting file couldn’t be imported to Rider 2018.3 (RIDER-22823).
  • The misplaced position of inline parameter name hints (RIDER-22452).

New in Rider 2018.3 Build 183.5047.86 (Jan 10, 2019)

  • Code Vision: try this new way of seeing useful information about your code right in the code editor. Usages, version control info, derived types, extension methods, and exposing APIs are now in plain sight, with no additional actions required!
  • Remote Debugging via SSH: need to debug an application on a remote machine? No problem, just call the action “Attach to Remote Process…” to attach to the process. .NET Full/Core, and Mono debuggers are supported.
  • Rename Project refactoring: no more manual renaming of all usages of a project. Call up this refactoring and you’ll be done before you know it.
  • Assembly Explorer now allows opening multiple assemblies, as well as traversing and exploring all open assemblies.
  • Zero-latency typing: even for smart typing assists that perform time-consuming tasks like reformatting code, Rider’s UI doesn’t get blocked and the editor stays smooth and responsive.
  • Launch Settings: support for launchSettings.json files is now available in ASP.NET Core projects.
  • We’ve redesigned the Search Everywhere popup and the Plugins pages in Settings.
  • Updated C# and VB.NET support includes improved C# 7 deconstruction support and language support for VB.NET 15.3 and 15.5.
  • An integrated performance profiler. Note that for now, the profiling features are only available on Windows.
  • Type Hierarchy tool window: explore the inheritance hierarchy of types via Navigate | Type Hierarchy.
  • Web development: from improved Angular support and better auto imports in JavaScript to debugging Node.js worker threads and support for TypeScript 3.1 features, and more.
  • VCS support: manage GitHub Pull Requests right in the IDE, and work with Git Submodules.
  • Android Development: lots of embedded tools and features from Android Studio are available, including a WYSIWYG designer, code completion for AXML/Android Manifest files, SDK/AVD Manager, and more.
  • Inline parameter name hints for C# and VB.NET are here.
  • Updated NuGet support offers Find this type on nuget.org, a new quick-fix to Install missing .NET Core Adapter, and better and faster search in the NuGet window.
  • New language injections: SQL and other IntelliJ IDEA language injections now cover C# string literals.
  • Updated F# support; brand new F# lexers work for both IntelliJ IDEA’s frontend and ReSharper’s backend; Rename refactoring works for local symbols; and there are new grouping types in Find Usages.
  • Updated Database support delivers one more NoSQL database, Cassandra, and several improvements in SQL code completion.
  • Unity support updated: New inspections keep a tight watch on the performance of your Unity code; collect method and class usages from scene/prefab/asset files; Unity Explorer is now shown on Linux; and more!
  • Other features: there’s a brand new engine under the hood of the expression evaluator; Ctrl+Click on an entity declaration now shows the usages; the refactorings Move to Resource, Inline Resource, Move Resource, and Rename Resource are now available; you can now ‘Build only this project without dependencies‘; and, as we love saying, there’s even more!

New in Rider 2018.2.3 Build 182.4231.496 (Sep 27, 2018)

  • Rider correctly calculates C# language version based on the latest value in a csproj file (RSRP-471483).
  • Azure DevOps URLs in NuGet Credential Provider is supported (RIDER-19664).
  • We’ve fixed the Unhandled Exception while running Unity in batchmode (RIDER-19688).

New in Rider 2018.2.1 Build 182.4231.348 (Aug 30, 2018)

  • Highlights:
  • Connection to Perforce works again (RIDER-18609).
  • NuGet authentication for private NuGet feeds has been fixed (RIDER-18125).
  • The spell checker stops warning about non-English comments, GUIDs, NuGet package names,
  • etc. (RIDER-19127).
  • The bug No connection string found was fixed in Entity Framework support (RIDER-19059).
  • The behavior of the setting Allow placement of caret after end of line has been fixed (RIDER-19088).
  • F5 now behaves as expected (RIDER-4575).
  • Bug:
  • RIDER-4575 — Run > Debug '[profile]' and F5 (in Visual Studio scheme) behave differently
  • RIDER-11234 — Support for Lazy in debugger
  • RIDER-18125 — Regression in NuGet authentication
  • RIDER-18167 — Entity Framework migrations doesn't work in 2018.2 EAP
  • RIDER-18609 — Cannot establish connection to Perforce anymore
  • RIDER-18698 — Write dotCover workspace host logs to a separate folder
  • RIDER-18766 — dotCover logs take enormous amount of space
  • RIDER-18807 — Cannot resize unhandled exception popup by dragging upper side and top-left corner
  • RIDER-18947 — Rider shows that whole node_modules folder is in index
  • RIDER-19059 — Entity Framework support stopped working in 2018.2 (no connection string found)
  • RIDER-19074 — LiveTemplates: attachedProperty > edit variables > nothing happens
  • RIDER-19088 — 'Allow placement of caret after end of line' setting not persisted
  • RIDER-19127 — All non-english comments are warned as typo
  • RIDER-19172 — Defines in Unity compiler response files are not detected
  • RIDER-19206 — Spellchecker shouldn't check GUIDs, NuGet package names etc
  • RIDER-19241 — NUnit test status is not updated
  • Exception:
  • RIDER-15437 — Not bound: RdSignal: `RoslynHost.RoslynModel.session.$.fileOnDiskChanged::`
  • RIDER-18707 — The lifetime has already been terminated. Object name: 'Lifetime'.
  • RIDER-18777 — Object reference not set to an instance of an object.
  • RIDER-18956 — The execution context must be guarded from reentrancy in order to execute this action.
  • Performance Problem
  • RIDER-18849 — Very slow code completions in Unity project
  • Usability Problem:
  • RIDER-18655 — Autosuggest stays open after value is selected.
  • RIDER-18656 — Autosuggest: Enter closes autosuggest instead of proceeding with the refactoring.
  • RIDER-18906 — Non-informative error message when .NET Project run configuration is selected for Xamarin project

New in Rider 2018.2 Build 182.4231.193 (Aug 23, 2018)

  • Debugger: call stacks are now displayed in a more understandable way, thread-specific breakpoints have been introduced, and inspecting and expanding unsafe pointers is now supported.
  • Docker support has reached the debugger: It is now possible to debug ASP.NET Core apps in a local (Linux) Docker container: inspecting variables, the stack frames, threads, as well as stepping through your own or decompiled third-party code.
  • Publishing: We have added two new run configurations: Publish to IIS and Publish to custom server. Currently, only publishing of ASP.NET Core Web projects is supported.
  • Code completion: we now use ReSharper’s statistics-based scoring algorithm to provide more relevant items higher in the code completion popup. Moreover, code completion now works in scratch files, debugger watches, and the C# Interactive tool window.
  • Solution Explorer redesign: a new toolbar with Show all files, Autoscroll to/from source and File Nesting Settings icons. The Solution Explorer now includes Scratches view, handles nested files better, and gets the File System and the Folders always on top modes.
  • MacBook Touch Bar support for the IDE, new icons, dark window headers on Mac.
  • dotCover comes to Rider: Unit test coverage and continuous testing are now available out of the box. It is currently only available on Windows for now but it is the first step towards dotCover integration on all supported platforms.
  • Integrated spell checking: ReSpeller plugin was finally merged to ReSharper and now it comes out of the box. Other updates included from ReSharper 2018.2: C# 7.3 support, initial Blazor support, and more!
  • Templates editor: You can now manage, add, and modify Live/Surround/File Templates right from the Rider settings.
  • Frontend development features: TypeScript 2.9/3.0 support, improved support for React, Angular, and Vue.js.
  • VCS update: Easier resolve of merge conflicts, enhancements in VCS Log tab, favorite branches in Branch filter, Browse repository at revision action, and more!
  • Unity support: support for .asmdef and csc.rsp files, an option to disable Unity Reload Assembles in Play mode, Unity players in the Attach to Unity Process list, a fix for the invalid warning for this == null in Unity types, improved support for debugging remote players, Packages and Scratches nodes in Unity Explorer, and more!
  • F# support: File Templates now work inside F# projects, F# 4.5 features like Span support and the match! keyword come to FSharp.Compiler.Service.
  • C# Interactive: a new Reference in the C# Interactive context menu is available to reference the selected assembly or project in C# Interactive tool window, and the debugger can be attached to C# Interactive tool window.
  • Unit Testing: Discovering and running tests in SDK-styled projects is now faster, a new lock/unlock icon has been added to the Unit Test Session toolbar, Unit Testing related actions have been added into the default keymap, and more.
  • NuGet support: We added a filter, format customization, and advanced diagnostics to NuGet logs, support for AutoReferenced packages and TLS-1.2-only NuGet feeds.
  • Roslyn Analyzers: This release comes with initial support for .ruleset files and stylecop.json settings are now respected.
  • Other features: Generate GUID, “Custom tools”, the Re-run action on the Find Usages tab, and Runtime arguments for Run/Debug Configuration are just some of the new cutting-edge features we have included.

New in Rider 2018.2 Build 182.4231.90 RC (Aug 16, 2018)

  • Bug:
  • RIDER-548 — Live templates not available for C#
  • RIDER-1258 — ReSharper host crashes when no space left on disk
  • RIDER-1270 — Find Usages "Rerun search" is not available
  • RIDER-1288 — Solution Explorer clips file names
  • RIDER-1795 — Extension "*.cs" is missing in File Mask(s) suggestions list in Full Text Search
  • RIDER-2072 — Inplace Rename hotspot should appear below the symbol
  • RIDER-2403 — Rider stops responding to input (soft crash) if closed while debugging.
  • RIDER-2513 — Debug class library hosted by external exe (NServiceBus.Host)
  • RIDER-3419 — Closing Parenthesis not being typed over when auto-inserted
  • RIDER-4251 — Missing parameter name in completion
  • RIDER-4430 — Wrap text or change it in Nuget confirmation dialog
  • RIDER-4695 — When button in NuGet disabled icon not changed it's looks little strange.
  • RIDER-4728 — 'Navigate To :: Unit test explorer' doesn't work
  • RIDER-4838 — Error in NuGet when project has the same name as NuGet package, for example, xunit
  • RIDER-5083 — Add the second quotation mark automatically in breakpoint condition
  • RIDER-5478 — There's no Alt+Enter popup in the scratch files
  • RIDER-5940 — Add Macro for current Configuration
  • RIDER-6060 — Nothing happens when clicking "More" in Unit Test popup
  • RIDER-6538 — breadcrumbs shows items hidden from the solution explorer, clicking leads to exceptions as there're no matching elements in the tree
  • RIDER-6559 — F#: autocomplete triggers inside string literals
  • RIDER-6869 — Show adequate error message if user (un)intentionally killed backend
  • RIDER-7028 — Support Paket Restore
  • RIDER-7568 — Starting rider crashes Cinnamon
  • RIDER-7684 — Diff window typing is in incorrect place
  • RIDER-7756 — Show node_modules packages differently depending on indexed/not-indexed state
  • RIDER-7778 — Complete methods with brackets in Evaluate Expression dialog
  • RIDER-7936 — Renamed file in Rider - not fully shown in SolutionExplorer
  • RIDER-7953 — Allow running nunit tests on custom mono on windows
  • RIDER-8013 — Breakpoints *are not hit* when set after starting a debug session, likewise breakpoints *are hit* when removed after starting a debug session.
  • RIDER-8152 — Expanding nguid template in quotes removes first quote
  • RIDER-8155 — Solution Explorer: Show folders on top
  • RIDER-8178 — Rider Changed csproj File Encoding
  • RIDER-8251 — Code completion for 'return' doesn't allow to type 'yield return'
  • RIDER-8476 — Show usages in 'Find Results' is checked and can't be changed
  • RIDER-8502 — Encapsulate field dialog doesn't update after unchecking "to auto-property"
  • RIDER-8504 — Change default File mask in Find in Path from *.mxml
  • RIDER-8631 — Rider reports an error in file, but build is successfull. Also xaml and xaml.cs files for on if views are shown as independent files in solution tree
  • RIDER-8637 — Unwanted code completion when typing float literal and switching focus between windows
  • RIDER-8857 — navigate > class cannot show my dll class
  • RIDER-8861 — Union representation accessibility is not respected in C#
  • RIDER-8938 — Test Output lines number is less than twice as it's set in Settings
  • RIDER-9130 — Inline object initialisation property suggestion is wrong
  • RIDER-9159 — Problem icons in NuGet
  • RIDER-9227 — Invalid Duplicate Definition
  • RIDER-9341 — Incorrect "is never assigned" inspection for Unity project.
  • RIDER-9388 — Rider allows to edit decompiled files
  • RIDER-9788 — Razor code block colors
  • RIDER-9804 — Rider doesn't respect in new .csproj format
  • RIDER-9810 — the first column is unnamed, the selected text must be white (i.e. foreground color)
  • RIDER-9868 — External Tools macros issue with solution files
  • RIDER-9908 — Files are duplicated in Solution Explorer
  • RIDER-9916 — Disable multiselection with Ctrl in NuGet packages search results
  • RIDER-10011 — blinking auto popup completion in the end of file
  • RIDER-10019 — [VB.NET] "From" keyword is not highlighted
  • RIDER-10061 — Unable to launch Rider - Reinstall required after crash - EAP v172.4144.808
  • RIDER-10150 — #region autocompletes when a keyword is in region name
  • RIDER-10408 — Not aligned edit project properties dialog
  • RIDER-10417 — Odd header row + the list should be disabled until the radio button will be checked
  • RIDER-10819 — Chars are not highlighted in VB
  • RIDER-10852 — Plugin-aware IconPatcher
  • RIDER-11072 — Unresolved symbols in .targets
  • RIDER-11095 — Unable to restore NuGet packages StyleCopAnalyzers solution
  • RIDER-11097 — Duplicating a XAML-file in the source folder
  • RIDER-11129 — .NET Core 1.1 app: once launched, have to reload projects to build
  • RIDER-11184 — Select in Project View Keymap no Longer Works in 2017.2
  • RIDER-11263 — by 'Add existing items' can't add any archives files
  • RIDER-11295 — Structure view always collapses its code regions upon each tab switch
  • RIDER-11358 — New console project fails to build
  • RIDER-11396 — Wrong project name in package spec
  • RIDER-11497 — Add diagnostics for .NET Core tests.
  • RIDER-11523 — При создании JSON файла через "New => JSON file" в начало файла добавляется символ с кодом 65279
  • RIDER-11654 — Improve "Group name expected" error message
  • RIDER-11701 — Inspection results. "Cancel" doesn't work in value tracking
  • RIDER-12006 — "Implicit evaluation disabled" for Watch objects
  • RIDER-12063 — Rider solution explorer does not open file on double click
  • RIDER-12088 — Red code after renaming or adding extern alias
  • RIDER-12239 — Invalid "make readonly" inspection for Serializable fields (Unity)
  • RIDER-12266 — Inspect Unsafe pointers just like non-unsafe structs & classes
  • RIDER-12304 — ANTLR generated files are not treated properly
  • RIDER-12339 — Add New Class with name ending with Backslash generates class without name
  • RIDER-12439 — Open File or Folder creates solution file
  • RIDER-12557 — Rider analysing auto-generated obj files on .NET Standard / .NET Core
  • RIDER-12670 — Incorrect path to msbuild is displayed in settings
  • RIDER-12686 — Surround With (Ctrl+Alt+T) not working on C# scripts since Rider 2017.3 update
  • RIDER-12741 — Cannot edit file properties for the file which has a nested file
  • RIDER-12743 — Attach folder does not work when folder is on Solution Level
  • RIDER-12749 — Path separator in indexLayout.xml on different OS
  • RIDER-12758 — F5 and Ctrl+F5 won't buld solution before run
  • RIDER-12794 — Xamarin Multiplatform Library - open MyPage.cs on project creation from template
  • RIDER-12800 — Debugger Watch: Implicit evaluation is disabled
  • RIDER-12873 — Evaluating expression shows "namespace" instead of value
  • RIDER-12935 — Hovering over variable containing long string shows blurred content of variable
  • RIDER-12955 — Conditionnal breakpoint & Evaluate and log features don't work
  • RIDER-12967 — Bad positioning of JetPopupMenu on scree edge
  • RIDER-13022 — ParameterInfo is not shown when typing fast
  • RIDER-13129 — False positive error in Core project depending on multitargeting project
  • RIDER-13180 — Override of ToString for Record, Union types is 'ambiguous' from C#
  • RIDER-13302 — Invalid crop line length in console output.
  • RIDER-13459 — Rider adds BOM to a new XML file even when setting "Create UTF-8 with NO BOM" is enabled
  • RIDER-13483 — edmx-file is not excluded completely
  • RIDER-13543 — Issues with Task management plugin
  • RIDER-13603 — While running Unit Tests, selecting a test from the list will not work correctly
  • RIDER-13683 — Move refactoring is broken
  • RIDER-13834 — EnumSelector control does not restore saved value
  • RIDER-13874 — 'You are about to move 1 folder' triggers CONSTANTLY
  • RIDER-13896 — C# file templates are not available when one call Ctrl+Alt+Ins in solution explorer for the first time
  • RIDER-13900 — Missing support for .NET Core 2.1
  • RIDER-13979 — Resx Designer.cs file is duplicated in Solution Explorer in "Show all files" mode
  • RIDER-13985 — Property not defined / empty string when building with msbuild
  • RIDER-14015 — Something went wrong placing &kb shortcuts in the labels of this refactoring dialog
  • RIDER-14173 — Exception popup is not shown for web based projects
  • RIDER-14221 — Support [DebuggerStepThrough] in 'Smart Step Into'
  • RIDER-14225 — "Condition" is displayed as an invalid attribute within HintPath tags in the .csproj file.
  • RIDER-14244 — Newly added classes to Shared Projects are not seen by Resharper
  • RIDER-14302 — Strange progress indicator is spinning forever
  • RIDER-14324 — csproj/fsproj editor dislikes EmbeddedResource LinkBase attribute
  • RIDER-14340 — 'Attach Existing Folder' doesn't allow to attach multiple folders
  • RIDER-14361 — Unresolved code from GitInfo NuGet package
  • RIDER-14393 — Hard-coded path to binary /usr/bin/stat instead of looking up for it in PATH
  • RIDER-14424 — Long rename popup in some cases
  • RIDER-14466 — MsBuild task running after Rider quit
  • RIDER-14558 — JetBrains MSBuild 15.5.180 issue
  • RIDER-14581 — Can't find symbols during code evaluation
  • RIDER-14587 — Nuget timeout but no other network issues present
  • RIDER-14589 — Solution Explorer shows incorrect structure for some arrangements of files with DependsUpon
  • RIDER-14626 — Roslyn Analyzers do not respect ruleset files
  • RIDER-14643 — Solution Explorer: project's Properties folder should have a fixed position in the list of project items
  • RIDER-14706 — Find in Files Tool Window
  • RIDER-14710 — SWEA in F# project tree
  • RIDER-14719 — When attaching on Debugger.Launch() Rider doesn't select nearest user frame
  • RIDER-14773 — Rider shows duplicated of projects in "Show all files" mode.
  • RIDER-14802 — Caret hang when moving with active parameter info.
  • RIDER-14807 — Can not run in Rider, but can in terminal
  • RIDER-14814 — Optional arguments defined in F# class methods are not optional in C#
  • RIDER-14828 — Using Create type/nested type and changing class to struct causes Rider to get confused about the type
  • RIDER-14838 — dragging a directory/file from project structure to terminal does not open terminal at directory
  • RIDER-14840 — Debugger does not work on full framework project on MacOS
  • RIDER-14846 — Code cleanup/reformat code for asmx, ashx
  • RIDER-14901 — Preview usages does not work
  • RIDER-14936 — Infinite progress in SolutionExplorer
  • RIDER-14978 — Some of Microsoft.TemplateEngine reference Newtonsoft.Json 8
  • RIDER-14996 — Ef Add-Migration Config File Items show view config
  • RIDER-15046 — Rider loses focus after navigation in tabless mode when Autoscroll from source is on (also affects Navigate back/forward)
  • RIDER-15072 — Remove XSL transformation for RunManager.xml
  • RIDER-15074 — Roslyn icon on the Analyzer nodes in the SolutionExplorer looks like an error
  • RIDER-15109 — TODO view infinite cyclic active file swap
  • RIDER-15127 — Don't exclude IDEA keymaps.
  • RIDER-15150 — Cursor does not move left/right after showing popup in completion lookup
  • RIDER-15162 — Searching solution explorer with Autoscroll to source
  • RIDER-15316 — Better item presentation in `Show instances` window
  • RIDER-15318 — Cannot upgrade Microsoft.NETCore.App package
  • RIDER-15338 — Missing quick action "Open recent" to display list of recently opened projects
  • RIDER-15339 — Port Attachment.openContentStream change to IDEA.
  • RIDER-15348 — Fix UnitTestRunConfiguration base on IDEA master
  • RIDER-15365 — An exception was thrown by the type initializer for Microsoft.Build.Evaluation.ProjectCollection
  • RIDER-15408 — Find Action dialog gets stuck with some queries
  • RIDER-15412 — Fix assert com.jetbrains.rider.completion.actions.RiderCodeCompletionHandler#customInsertItem
  • RIDER-15435 — Move TeamCityHelper.groovy to IDEA
  • RIDER-15441 — When double-clicking files in Solution Explorer, you need two "Back" actions to go back to the previous file
  • RIDER-15467 — [.NET Core] (csproj) Visible attribute not recognized
  • RIDER-15504 — 2018.1 - Rider Unable to Read NuGet Feeds
  • RIDER-15514 — Unable to deploy Xamarin.iOS or Xamarin.Android projects
  • RIDER-15558 — MSBuild Autodetection doesn't depend on C# Version flag "latest"
  • RIDER-15599 — Unclear message in case of missed .NET Framework
  • RIDER-15601 — Code analysis hangs when loading solution
  • RIDER-15630 — All declarations inside a method are incorrectly shown as not used after using completion
  • RIDER-15638 — Moving empty folder to empty folder removes the first folder from csproj
  • RIDER-15665 — Can't set custom msbuild in settings
  • RIDER-15739 — Remove "Use ReSharper formatter settings on Tab" option from settings
  • RIDER-15748 — Alt-Enter works once at a time (Mac)
  • RIDER-15867 — Can't add existing project on different drive
  • RIDER-15870 — Javascript debugger not attaching in latest Rider 2018.1 on Mac OS High Sierra
  • RIDER-15874 — "Inspections are off" for files opened in editor after project reopen
  • RIDER-15890 — Wrong exe path in the run config. dialog after project change.
  • RIDER-15926 — Rider 2018.1 hangs on loading dotnet core 2.1 project
  • RIDER-15951 — NuGet Search Never completes, nuget.org is up
  • RIDER-15957 — Ugly message about missed TFM on the NewProject screen
  • RIDER-15977 — In-memory documents with backend content model
  • RIDER-15984 — "Show Hidden Files and Directories" doesn't help to see ignored names in OpenFileDialog
  • RIDER-16019 — Weird debugger behavior with dynamic cast
  • RIDER-16030 — Constantly re-prompted to enter nuget feed credentials
  • RIDER-16076 — Fix attach to local process
  • RIDER-16079 — Shortcut for "Attach to Local Process..."
  • RIDER-16083 — Live templates does not respect editable field instance setting
  • RIDER-16108 — Extensible way to add tabs to Rider Run Configuration
  • RIDER-16109 — Empty space in context menu of Dependencies
  • RIDER-16125 — Swea hangs
  • RIDER-16140 — Debugger doesn't recognise Count of a List property
  • RIDER-16141 — Late daemon rehighlight after completion
  • RIDER-16151 — Frequent freezing and typeahead errors
  • RIDER-16163 — Autocomplete is used inside F# multi-line comments (`(*` and `*)`). This makes using Enter difficult inside multi-line comments.
  • RIDER-16177 — Rename in Database Tool
  • RIDER-16198 — There is no notification 'Run npm install' on opening .net core web template
  • RIDER-16251 — Breakpoint icon is mislocated
  • RIDER-16253 — Step Over works incorrectly
  • RIDER-16262 — Obsolete members are not displayed crossed out in code completion
  • RIDER-16268 — Reformat Selection available for F# but doesn't work
  • RIDER-16269 — Structural navigation settings should not be available in Rider settings as long as structural navigation is not implemented in Rider
  • RIDER-16275 — file colors doesn't work on files which are not in prj
  • RIDER-16291 — Unable to Use a NuGet Server set up with TLS 1.2
  • RIDER-16296 — "Rename File..." action in context-menu of tab does not work.
  • RIDER-16300 — File -> Open shows opened recent solutions
  • RIDER-16310 — Parameter info content disappears when changing cursor position with Left, Right arrows
  • RIDER-16314 — Rider dot track files imported by * from imported target. An example our ParserGen.
  • RIDER-16322 — Incorrect icons theme in the latest dev build.
  • RIDER-16324 — Cannot authenticate private nuget package feed through VSTS with 2FA enabled
  • RIDER-16325 — Restore button should be shown on each panel in NuGet Tool Window
  • RIDER-16330 — Different extract method in VS and Rider (no support for extracting local functions in Rider)
  • RIDER-16335 — Changes in file are not passed to same file in different project context
  • RIDER-16350 — Update EAP splashes for 182
  • RIDER-16366 — TypeScript Completion: Class fields and keywords take precedence over local variables
  • RIDER-16387 — MSBUILD : error MSB4016: The build stopped unexpectedly because the "ReusableLogger" logger failed unexpectedly during initialization. Couldn't extract directory from path: []
  • RIDER-16390 — Razor debugging not found associated module for breakpoint
  • RIDER-16393 — TypeScript Completion: problem with arrow functions when typing fast
  • RIDER-16394 — Change Signature Rider: UI issues.
  • RIDER-16397 — Don't use console logger in MSBuild task.
  • RIDER-16399 — Memory leak in DotNetProjectProfilingConfigurationEditor in tests
  • RIDER-16438 — Shader text is blinking when typing in HLSL/GLSL/Cg
  • RIDER-16454 — Cannot change Xamarin Android SDK and NDK Folders
  • RIDER-16455 — Don't use italic in NuGet logs
  • RIDER-16456 — Prefer mono doesn't work for Debug Unit tests.
  • RIDER-16462 — Download JDK on PWC only when it not exists and IDEA not running.
  • RIDER-16470 — Support AutoReferenced NuGet packages
  • RIDER-16474 — Black ugly icons in installation wizard (Default plugins page)
  • RIDER-16486 — Convert Indexer To Method Rider: UI issues.
  • RIDER-16488 — Dialogs Rider: UI issues.
  • RIDER-16489 — Make Method Non Static Rider: keyboard-only input issues.
  • RIDER-16490 — Make Static Rider: UI issues.
  • RIDER-16497 — Change Signature: modifiers are not displayed and can not be selected.
  • RIDER-16498 — F# record constructor calls do not considered as the same symbol in C# code
  • RIDER-16500 — Extract Members To Partial Rider: UI issues
  • RIDER-16504 — tt symbols are printed in Build output
  • RIDER-16506 — Changing debugger settings aren't applied for current session
  • RIDER-16507 — Extract Method: UI issues
  • RIDER-16514 — Extract Method: Visibility changes are not shown in Signature preview.
  • RIDER-16529 — Misleading error "The default XML namespace of the project must be the MSBuild XML namespace" when MSBuild 15 is not installed
  • RIDER-16644 — A mess in the context menu of items in solution explorer
  • RIDER-16670 — Editing decompiled source popups on project reload
  • RIDER-16671 — Solution explorer tree is not updated after changes
  • RIDER-16699 — Run configuration is not created for F# console app template
  • RIDER-16701 — [New Solution Explorer] Project -> Show history changed its behaviour
  • RIDER-16705 — Encapsulate Field Rider: UI issues
  • RIDER-16706 — Encapsulate field: accelerators issues
  • RIDER-16717 — Incoming Calls via Alt Enter are not available on method declaration
  • RIDER-16719 — Encapsulate Field: public property is created when visibility changed to not public.
  • RIDER-16721 — Cannot create a run configuration
  • RIDER-16726 — Extract Method: return type should be selected twice to update member's list and preview.
  • RIDER-16729 — Weird behavior with build configurations
  • RIDER-16732 — Extract Method: Move Up/Down buttons are not moving parameter up/down.
  • RIDER-16733 — Space in TargetFrameworks makes framework id unknown
  • RIDER-16734 — [New Solution Explorer] Exception thrown on attempt to move file into folder where file with same name exist. Exception: TextBasedThrowable: null
  • RIDER-16756 — Custom color scheme for XML is not applied to .config files in Editor
  • RIDER-16757 — Add EmptySolution to existing solution folder
  • RIDER-16765 — Choosing Code Cleanup or Reformat Code does nothing
  • RIDER-16769 — Impossible to delete scratch file from solution explorer
  • RIDER-16776 — infinite caching
  • RIDER-16778 — Pointers in Unity don't work
  • RIDER-16784 — error throw trying to read a scriptable object after returning from play mode
  • RIDER-16801 — Rider repeats user input
  • RIDER-16831 — [New Solution Explorer] Exception thrown on copypaste file with same name (in excluded folder)
  • RIDER-16834 — Broken icon patcher after IDEA merge.
  • RIDER-16839 — Unable debug after update to .NET Core 2.1
  • RIDER-16852 — Special words matching is broken in Go to File Member
  • RIDER-16861 — Using refactoring "extract class to a separate file" when finished focuses solution tree instead of a new file
  • RIDER-16880 — Completion hangs inside class attribute
  • RIDER-16888 — Rider confuses a cs file in a shared project referenced by multiple projects in a solution as multiple files
  • RIDER-16914 — Case sensitiveness when running tests
  • RIDER-16928 — "Unity Engine" page in Rider settings is empty
  • RIDER-16939 — Breakpoints do not hit if Fody library is used and interface argument is used in constructor
  • RIDER-16942 — Accepting an autocomplete that replaces a symbol breaks whole file's parsing.
  • RIDER-16951 — Can't inspect / watch static c# variables
  • RIDER-16962 — File moved from one project to another is not recognized as project file until the project is not unload and then reload.
  • RIDER-16971 — Typescript Autocomplete Recommendations Don't Make Sense
  • RIDER-16997 — Introduce Field Rider: UI issues
  • RIDER-16998 — Introduce Field Rider: accelerator's issues.
  • RIDER-17005 — Support F# 4.1 struct unions and records
  • RIDER-17008 — Add support stack-traces for PPDB in Rider backend.
  • RIDER-17009 — Relayout Generate dialog
  • RIDER-17028 — Project context selector not visible in second instance
  • RIDER-17029 — Exceptions in Generate break all backend features
  • RIDER-17049 — "Copy to output directory" disappears after file rename
  • RIDER-17060 — Folders at top not working correctly
  • RIDER-17063 — Rider switches explorer mode when creating new files.
  • RIDER-17094 — Wrong icon for node in dependecies
  • RIDER-17095 — Disable injected language fragment highlight by default for Cg/HLSL
  • RIDER-17158 — Rename Rider: accelerator's issues.
  • RIDER-17166 — Rename Rider: UI issues.
  • RIDER-17172 — "Toolset and Build" page is empty
  • RIDER-17194 — [New Solution Explorer] Do not expand tree on D'n'D folder with content
  • RIDER-17206 — Inconsistent Enter behaviour when completing an item
  • RIDER-17214 — xUnit theories with inline data do not refresh properly when the data changes
  • RIDER-17218 — Hard focus lookup in inline rename of reference
  • RIDER-17224 — Unable to insert breakpoint in lambdas inside base constructor parameters list
  • RIDER-17232 — Fails to refactor in shared file solutions
  • RIDER-17247 — Upgrading packages does not invalidate package view
  • RIDER-17272 — android debug for unity doesn't work
  • RIDER-17276 — Do not show method as unused when it is being used in a Unity Editor
  • RIDER-17287 — ShaderLab keywords are not highlighted
  • RIDER-17292 — Unable to build projects: (The type or namespace name '...' could not be found (are you missing a using directive or an assembly reference?)
  • RIDER-17301 — Can't change scope (solution, project ...) in "Find in path"
  • RIDER-17307 — ... is not recognized
  • RIDER-17310 — Cannot run Xamarin.iOS app from Windows on the connected device
  • RIDER-17311 — Cannot run Xamarin.iOS app from Windows on a simulator
  • RIDER-17312 — Cannot open project with apostrophe in name
  • RIDER-17313 — Unhandled exceptions are ignored (debug of Xamarin.iOS)
  • RIDER-17316 — Impossible to choose directory in Find In Path
  • RIDER-17331 — [2018.2 EAP] Big solution freeze
  • RIDER-17336 — Bad colors in ParameterInfo
  • RIDER-17342 — Broken Entity Framework modals in 2018.2 EAP
  • RIDER-17361 — 'Not build' suffix
  • RIDER-17377 — Rider Internal mode via Toolbox does not work on Windows
  • RIDER-17384 — New Unit test gutter icons are giant and noticeably change size when test success/fail
  • RIDER-17400 — Rebuild solution seems broker in Rider 2018.2 EAP
  • RIDER-17402 — Extract Method Rider: checkboxes that are not clicked are checked/unchecked.
  • RIDER-17414 — Project templates are missing if I want to add project in Empty solution
  • RIDER-17421 — It's impossible to run projects without an sln file
  • RIDER-17435 — Fix docker plugin
  • RIDER-17448 — Do not check names of implemented interface members (in compiled code?) for typos
  • RIDER-17475 — Fix Docker plugin in installer.
  • RIDER-17482 — F# scratch files do not have proper icons
  • RIDER-17484 — Internal IDE Error when ending XAML comment without beginning
  • RIDER-17501 — With new code completion in Debugger watches, Debugger cannot sometimes evaluate the imported expression
  • RIDER-17510 — Unity closes when loading Rider's Unity Plugin
  • RIDER-17520 — Internal IDE Error when creating empty XAML file
  • RIDER-17530 — Endless "synchronising projects"
  • RIDER-17538 — dotCover actions shouldn't be shown at macOS.
  • RIDER-17557 — Incorrect spellchecker behaviour
  • RIDER-17558 — Cmd+K shortcut is not working anymore on MacOs X
  • RIDER-17566 — Publishing: newly added "Publish profile" on "Create Run Configuration" page does not appear in drop-down list until page reopen
  • RIDER-17568 — Remove non-.NET ReSharper live templates
  • RIDER-17571 — Rename: parent checkbox in Rename Related Symbols dialog contains icon which changes when dialog resized.
  • RIDER-17572 — Rename: in Rename Related Symbols dialog if parent checkbox is checked/unchecked visible child checkboxes should be focused to display changes.
  • RIDER-17573 — Rename Related Symbols dialog: checkboxes are not checked/unchecked by space.
  • RIDER-17580 — File Templates ->Availability configuration: scroll goes to right when clicking on title in table.
  • RIDER-17581 — File Templates: no tooltips for buttons.
  • RIDER-17582 — File Templates: layout changes when selecting C# ->"Resources" template.
  • RIDER-17583 — File Templates: template is not selected when navigate to File Templates -> language first time.
  • RIDER-17585 — File Templates -> Availability configuration: column for checkbox is too wide and can not be reduced.
  • RIDER-17586 — File Templates -> Availability configuration: dialog is opened small.
  • RIDER-17587 — File Templates -> Availability Configuration: language is not selected when dialog opens
  • RIDER-17588 — Publishing: can not publish to Local IIS if Rider launched from Toolbox. Relaunch with elevated previligies does not work
  • RIDER-17590 — File Templates -> Availability configuration: checkboxes are checked/unchecked by its own.
  • RIDER-17591 — File Templates -> Edit variables: dialog opens small.
  • RIDER-17593 — File Templates -> Edit variables -> Choose macro: can't scroll to the bottom by dragging scrollbar.
  • RIDER-17594 — File Templates -> Edit variables: "Change macro" button is resized to match the description.
  • RIDER-17595 — File Templates -> Edit variables -> Choose macro: radio button is not selected when dialog opens.
  • RIDER-17598 — dotCover can show incorrect covering tests list on line-markers
  • RIDER-17603 — Stuck synchronizing projects
  • RIDER-17605 — Speller does not recognize escaped chars
  • RIDER-17609 — Extract Method: Layout changes when "Make virtual" checkbox is clicked.
  • RIDER-17612 — Extract Method: Name column width can not be reduced
  • RIDER-17614 — File Templates -> Edit variables: unmeaningful dialog is shown.
  • RIDER-17638 — Text editor blinks when coverage markers are redrawn.
  • RIDER-17640 — dotCover plugin activation dialog is shown on macOS
  • RIDER-17642 — "Updating counters..." background process appears twice when selecting a test in the Unit Tests tree and "Show coverage info for selected tests" mode is on
  • RIDER-17657 — Broken unit tests gutters because ".NET Core SDK is too modern"
  • RIDER-17667 — Unable to dismiss suggestions in rename dialog
  • RIDER-17677 — File Templates: can't change layout.
  • RIDER-17678 — File Templates: selection is not moving when navigate through templates using up/down keyboard arrows.
  • RIDER-17681 — File Templates -> Availability configuration: table with project types is not resized.
  • RIDER-17688 — File Templates -> Edit variables -> Choose macro: dialog opens small.
  • RIDER-17689 — File Templates -> Edit variables -> Choose macro: list of macros is not resized when dialog is resized.
  • RIDER-17691 — File Templates -> Edit variables: layout changes when variables are selected.
  • RIDER-17705 — File Templates -> Edit variables: dialog is not closing on Esc.
  • RIDER-17711 — Namespaces aren't shown in Go to Type navigation
  • RIDER-17712 — Crash when correcting a typo
  • RIDER-17721 — New code completion in Debugger watches sometimes doesn't work
  • RIDER-17722 — Completion: the closest match is not on top
  • RIDER-17723 — Lots of "Multiple highlighter registration" warnings in Rider logs when covering unit tests
  • RIDER-17733 — Unit Test Autobuild is not silent anymore
  • RIDER-17734 — Scroll is missing on "Toolset and Build" page
  • RIDER-17738 — Context actions from CMD support plugin are missing in solution explorer
  • RIDER-17748 — "Pin" in "Goto class" dialog is broken
  • RIDER-17750 — There is no "Cover Unit Tests" action in editor's context menu
  • RIDER-17758 — Second click on radio button unselects it.
  • RIDER-17761 — Tree collapses in Unit Tests Coverage window when browsing through tree in a unit test session with "Selected Tests in Active Session" option enabled
  • RIDER-17764 — Strings containing a null character are hard (not) debuggable
  • RIDER-17770 — string containing ASCII char '0' does not show correct value in debugger
  • RIDER-17775 — Completion items sorting: static methods have more priority than local variables
  • RIDER-17799 — Debugger problems with Unity projects
  • RIDER-17800 — Change Signature: return type does not change.
  • RIDER-17806 — There is no upgrage icon / button in NuGet toolwindow
  • RIDER-17808 — false installed packages '0' into Solution
  • RIDER-17831 — Restore doesn't work after external change with new NuGet.config file
  • RIDER-17844 — Bug with update of 'Conditional expression' and 'Evaluate and log' tabs
  • RIDER-17845 — Can't tab complete in introduce field
  • RIDER-17899 — Encapsulate Field: navigation by keyboard is impossible when Choose property appears.
  • RIDER-17900 — Encapsulate Field: Choose property dropdown color is different from visibility color.
  • RIDER-17903 — We are syncing first typed letter every time if virtual spaces are allowed
  • RIDER-17905 — Introduce Field: "private protected" field is created when "private" visibility is selected.
  • RIDER-17906 — Completion is not opened on Ctrl+Space.
  • RIDER-17915 — Completion issues
  • RIDER-17917 — Change Signature: "this" modifier is not disabled.
  • RIDER-17918 — Continuous Testing should make Unit Tests tool window active
  • RIDER-17935 — Profile Backend action flushes snapshot to invalid location
  • RIDER-17938 — Roslyn analyzers fail to load
  • RIDER-17941 — Bad code completion suggestion
  • RIDER-17981 — settings > language defaults issue
  • RIDER-17983 — Two instances of Rider opened when I open files from Unity
  • RIDER-17987 — Unit Tests Coverage tool window state (sorting, tree expansion, column widths) is not restored after Rider restart
  • RIDER-17992 — Rider does set the language level to C#7 although C#7.2 would be supported
  • RIDER-17993 — Remove ReSpeller actions for IDEA
  • RIDER-17998 — Replace Anonymous With Named Type: radio buttons are not selected when dialog opens.
  • RIDER-18000 — Convert Method To Property: textbox is too big.
  • RIDER-18002 — Convert Property To Method: impossible to complete refactoring using keyboard only on property without getter.
  • RIDER-18008 — Inconsistent NuGet Toolwindow UX for .net core project with multiple target frameworks.
  • RIDER-18015 — runRider.cmd isn't work on macOS.
  • RIDER-18017 — Nuget isn't showing installed packages per project
  • RIDER-18057 — code highlighting stops updating
  • RIDER-18060 — Hard selection in completion during rename refactoring
  • RIDER-18062 — dotCover takes too much of UI thread
  • RIDER-18068 — Evaluation doesn't work for some completed statements.
  • RIDER-18071 — ToImmutableList has better scoring than ToList
  • RIDER-18085 — Dragging file into editor opens new frontend instance
  • RIDER-18094 — Refactoring features stop working - platform eventually hangs
  • RIDER-18104 — Roslyn analyzers don't work on projects without sln
  • RIDER-18110 — Sandbox file imports list is empty on completion after reopening watch tab
  • RIDER-18125 — Regression in NuGet authentication
  • RIDER-18137 — do! is not colored as keywords
  • RIDER-18138 — FCS doesn't see external changes from git
  • RIDER-18151 — Incorrect fame view presentation for yield methods
  • RIDER-18153 — After updating mono Rider is still using old WellKnownProperties
  • RIDER-18154 — Combobox size
  • RIDER-18156 — Can't build F# project template with the following error : .NETFramework,Version=v4.7.1.AssemblyAttributes.fs(2, 26): [FS1108] The type 'ValueType' is required here and is unavailable. You must add a reference to assembly 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
  • RIDER-18169 — Can't log into Github account
  • RIDER-18174 — Change Signature: Modifier dropdown shows as selected.
  • RIDER-18175 — Change Signature: gaps in selection.
  • RIDER-18181 — No borders in table.
  • RIDER-18187 — Click on checkbox label checks/unchecks checkbox.
  • RIDER-18190 — Stop showing Vim backup files in Unity Explorer
  • RIDER-18192 — Extract Method: layout changes when dialog is resized
  • RIDER-18199 — Project model is being reloaded all the time
  • RIDER-18200 — Search in Explorer toolwindow is inconsistent
  • RIDER-18234 — Make publish feature more discoverable
  • RIDER-18246 — Two .Net Framework 4.0 entries in framework dropdown (new project dialog)
  • RIDER-18267 — Live Templates completed by space insert the name of template instead of expanding it
  • RIDER-18271 — Heap Allocation Viewer plugin is busted in the current version of EAP
  • RIDER-18280 — JetBrains.ReSharper.Host64.exe Crashes with StackOverflowException
  • RIDER-18307 — File Templates: newly created template is not selected.
  • RIDER-18309 — File Templates: no selection after template is deleted.
  • RIDER-18310 — File Templates: only 1 template is created if clone button is clicked several times.
  • RIDER-18311 — File Templates -> Edit variables: maximum size of left panel is too small.
  • RIDER-18319 — 18.2 EAP: Autocompleting an input in the pattern d+[dflu] prefers symbols matching that pattern, as opposed to numeric literals
  • RIDER-18320 — File Templates -> Edit variables: no selection sometimes.
  • RIDER-18329 — File Templates: layout changes for some templates.
  • RIDER-18330 — Parenthesis around first function parameter are not highlighted properly
  • RIDER-18335 — Live Templates: no "Mnemonic could be single digit only" error.
  • RIDER-18339 — Live Templates: empty template in template's list is shown for shortcut which starts with '= 1
  • RIDER-16396 — Not initialized
  • RIDER-16415 — ArrayIndexOutOfBoundsException: -1
  • RIDER-16508 — Sequence contains no matching element
  • RIDER-16536 — ArithmeticException: Catch: / by zero (/ by zero)
  • RIDER-16538 — One or more errors occurred., reason: System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.ArgumentNullException: Value c...
  • RIDER-16680 — [New Solution Explorer] TextBasedThrowable: null
  • RIDER-16753 — TextBasedThrowable: null
  • RIDER-16851 — IllegalStateException: Not bound
  • RIDER-16910 — null
  • RIDER-16927 — null
  • RIDER-17050 — Maybe you forgot to promote db version? Map=[SolutionBuilderRequestDataStorage::ReceivedMessages, 16]. FQN of requested type (JetBrains.ProjectModel.Features.SolutionBuilders.BuildRequestStor...
  • RIDER-17162 — null
  • RIDER-17167 — Not initialized
  • RIDER-17179 — Object reference not set to an instance of an object.
  • RIDER-17180 — null
  • RIDER-17385 — Object reference not set to an instance of an object.
  • RIDER-17388 — null
  • RIDER-17592 — Value cannot be null. Parameter name: value
  • RIDER-17626 — A task was canceled.
  • RIDER-17653 — DocumentRange is invalid
  • RIDER-17692 — Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
  • RIDER-17702 — Analyzer 'JetBrains.ReSharper.Plugins.Unity.Json.Feature.Services.Daemon.AsmDefReferencingSelfProblemAnalyzer' thrown exception: Object reference not set to an instance of an object.
  • RIDER-17756 — Catch
  • RIDER-17765 — Waiting in FireOutgoing more than 30000 ms. Possible livelock. Breaking
  • RIDER-17798 — Exception with Unity breakpoint with "log and evaluate" enabled
  • RIDER-17828 — Catch
  • RIDER-17901 — Object reference not set to an instance of an object.
  • RIDER-17914 — null
  • RIDER-17926 — This operation requires a reader lock. Use 'using (ReadLockCookie.Create()) { ... }'.
  • RIDER-17927 — The virtual spaces count must be nonnegative. Parameter name: virtualDelta Actual value was -3.
  • RIDER-18033 — Failed to complete 'str' in watch
  • RIDER-18036 — Error when trying to apply "Constructor to factory method" refactoring to external source
  • RIDER-18083 — PersistentIndexManager was requested about illegal index: 0
  • RIDER-18105 — Exception thrown with latest Rider SDK
  • RIDER-18212 — Catch
  • RIDER-18262 — null
  • RIDER-18297 — null
  • RIDER-18308 — Catch
  • RIDER-18377 — KotlinNullPointerException when browsing diff with Structure tool window opened
  • RIDER-18378 — Catch
  • RIDER-18686 — Argument for @NotNull parameter 'pane' of com/intellij/util/ui/UIUtil.decorateWindowHeader must not be null
  • RIDER-18689 — Not bound in RiderSolutionEventsTracker
  • Feature:
  • RIDER-742 — Add Docker support to debugger
  • RIDER-2392 — The IDE could use a spell checker
  • RIDER-2417 — Make smart replace "." into "->" for unmanaged pointers while typing
  • RIDER-3307 — Add an option to hide test output
  • RIDER-4395 — Semantic code highlighting in scratches
  • RIDER-4409 — add option to disable "Inactive preprocessor branch" warnings
  • RIDER-5375 — Custom mono arguments
  • RIDER-5658 — Create F# file templates
  • RIDER-6080 — A way to rename and lock/unlock unit tests sessions
  • RIDER-6602 — Need to show whitespaces in C#/VB code style previews
  • RIDER-7615 — generate simple XAML Xamarin forms with code behind class
  • RIDER-8956 — Add Xaml + Code Behind new file support
  • RIDER-10831 — Add the possibility to change authentication for ASP.NET projects
  • RIDER-11603 — Automatically create run configurations based on values in .csproj.user
  • RIDER-11649 — C# interactive doesn't have code completion.
  • RIDER-12840 — how to create a guid
  • RIDER-12898 — Focus build window on build
  • RIDER-13571 — Provide ability to set breakpoint only for current thread
  • RIDER-14080 — Support suggestions in hot spot sessions
  • RIDER-14126 — Allow set up depends upon project property from UI
  • RIDER-14237 — Help -> Enable YourKit agent action shows "Are you sure you want to exit Rider?" window
  • RIDER-14342 — Add "Show import items in basic completion" settings option from ReSharper
  • RIDER-14410 — Add a search to Unity Log
  • RIDER-14538 — Support external tools for resource generation
  • RIDER-14671 — Migrate to NuGet 4.7
  • RIDER-14745 — Add an option to remove the hammer/lightbulb icon from the gutter
  • RIDER-14860 — Support for "Custom Tool" in file properties
  • RIDER-14882 — Discover sln/csproj file when opening folder
  • RIDER-15175 — Create 'Uncomment action' only for Rider with appropriate shortcuts
  • RIDER-15211 — Order trace scenario by name.
  • RIDER-15297 — Unity explorer: implement 'autoscroll to/from source' and 'locate current file in explorer' action
  • RIDER-15970 — Support NuGet package management for Web site projects
  • RIDER-16067 — C# Interactive - Provide option to load all referenced assemblies
  • RIDER-16158 — Connect interactive c# to current debug session
  • RIDER-16226 — Register Rider as well-known editor for supported file types on macOS.
  • RIDER-16255 — Rider should support pyproj project files
  • RIDER-16342 — Provide a way to customize NuGet log output format
  • RIDER-16365 — Rider should discover and run unit tests in SDK-style projects which target .NETFramework without installed .NET Core SDK
  • RIDER-16520 — Make task bar and Dock build notification optionally.
  • RIDER-16543 — Support evaluation of expressions containing aliases
  • RIDER-17212 — Cannot disable break on unhandled exception
  • RIDER-17305 — Color scheme settings for ShaderLab
  • RIDER-17389 — MSBuild-based NuGet restore
  • RIDER-17395 — Keybindings in ReSharper VS Scheme: Word Wrap, Show Whitespace
  • RIDER-18150 — Log real path to build tool/mono along with symbolic links
  • RIDER-18159 — Add "Create Run cofiguration" into context menu for .pubxml profiles.
  • RIDER-18482 — Cannot publish a self-contained .NET Core app to a folder
  • Meta Issue:
  • RIDER-16132 — Migrate NuGet package reading from v2 to v4
  • Performance Problem:
  • RIDER-6325 — Rider becomes unresponsive when deleting huge NuGet feed
  • RIDER-6986 — Rider freezes on completion after '}' on interface/class/method end
  • RIDER-7669 — Cache NuGet cache size
  • RIDER-10262 — NuGetSolutionManager on startup
  • RIDER-10273 — Nuget toolwindow is hidden, but I see 500MB of mem traffic caused by NuGetSearcher.UpdateView
  • RIDER-14319 — Add file menu (Alt-Insert) in solution tree freeze UI for 3-5 sec on first call
  • RIDER-16906 — Rider requires frequent restarts due to hanging UI
  • RIDER-17036 — Zombie mono-sgen
  • RIDER-17340 — Deadlock in NuGetContentFileStorage::UpdateProjectInternal On Solution Close
  • RIDER-17430 — Sometimes Rider spend minutes trying to resolve a breakpoint
  • Task:
  • RIDER-8250 — An API for provide additional nodes in Solution Explorer
  • RIDER-14329 — Merge Scratch View and Solution Explorer
  • RIDER-15069 — Remove XSL transformation for VcsExtensions.xml
  • RIDER-15274 — Check that Unitys custom Roslyn analyzers work in Rider
  • RIDER-15591 — Split platform manager in Shell and Solution parts
  • RIDER-16236 — Add shortcut for RiderNavigateFromHereAction in $default
  • RIDER-16477 — Move Activate*ToolWindow shortcuts to the default keymap
  • RIDER-16865 — Use native idea icons
  • RIDER-16940 — Add documentation for Mono Remote run configuratuion
  • RIDER-17386 — [Unity] Add "Attach to Unity process" to the Unity action dropdown
  • RIDER-17847 — Make uninstall feedback work
  • RIDER-17873 — Add back-end info to the third-party software list
  • Usability Problem:
  • RIDER-2106 — If the program is finished with exit code 0 there is no notification on log about it (in IDEA when program is finished there is a log line like "Process finished with exit code 0", in Rider there is no such line)
  • RIDER-4123 — NuGet: Similar project names leads to unclear project choice
  • RIDER-7296 — Solution Explorer doesn't make it clear that projects are unloaded when there are solution folders
  • RIDER-7670 — Clear multiple NuGet caches
  • RIDER-8234 — Ability to show a standard Intellij/Rubymine Project View (Alt+F1) rather than Solution Explorer
  • RIDER-9669 — "Compare with..." in solution view
  • RIDER-9683 — "Restore skipped" balloon pops us every time build starts
  • RIDER-11154 — Documentation for Rider+Xamarin
  • RIDER-12698 — Add "Automatically insert parentheses after completion" option to Rider settings
  • RIDER-12764 — Showing Unity code source is less usefull than showing only declarations
  • RIDER-13484 — When opening a folder (not solution) folder are not displayed on the top
  • RIDER-13700 — Improve SolutionFolder context menu in SolutionExplorer
  • RIDER-13969 — AutoCompletion always imports symbols
  • RIDER-14260 — Discoverability: add 'Attach folder to solution' action to excluded folder in the context menu
  • RIDER-14613 — Use a distinct icon for the Properties folder
  • RIDER-14667 — Generate window's default size doesn't accommodate information that it contains
  • RIDER-15631 — Make .cshtml.cs files nest under .cshtml files by default
  • RIDER-15687 — Can't rebuild solution with Roslyn analyzers when Rider opened
  • RIDER-15744 — Entity Framework dialog shows different config files with same name
  • RIDER-15922 — Rider exception breakpoint dialog isn't resizable
  • RIDER-15992 — Decompiler/external symbols settings page in Rdier
  • RIDER-16078 — 'Add' submenu for not found files is not really helpful
  • RIDER-16080 — Move UnitTest shortcuts from 'Rider' keymap to 'Default' keymap
  • RIDER-16172 — nested files are not revealed with viewfinder (scroll from source)
  • RIDER-16196 — open parent of nested files usability problem
  • RIDER-16355 — UnitTest panel's Group button has issues
  • RIDER-16410 — Language level 'latest' is not available after level is changed.
  • RIDER-16431 — Run configuration with unloaded project changes project when selected
  • RIDER-16596 — Code completion doesn't remember and case insensitivity doesn't work
  • RIDER-16650 — Show exception popup in any context where exception object is accessible
  • RIDER-16907 — Improve notification about full pdb for sdb
  • RIDER-17535 — Open folder as solution
  • RIDER-17541 — Improve UI for Create Backend Thread Dump action
  • RIDER-17695 — File Templates -> Quick list: after move item to/from quick list moved item is not selected.
  • RIDER-17810 — Completion items priority. Prefix match should have higher priority than middle match
  • RIDER-17929 — With Continuous Testing on Save the make the Build Window Active, i can't continue editing.
  • RIDER-18317 — File Templates: if template is available in many project types then page layout can not be changed.
  • RIDER-18328 — File Templates: newly created template is cleared if another template is selected.
  • RIDER-18501 — Completion and language support for launchSettings.json
  • RIDER-18531 — disappearing watch 'view' button

New in Rider 2018.2 Build 182.4129.120 EAP 7 (Aug 11, 2018)

  • Unity support:
  • dotCover features have been disabled for Unity tests because they are not yet supported.
  • Packages and Scratches nodes have been added to Unity Explorer.
  • Support for Roslyn C# compiler response file (csc.rsp) has been introduced.
  • Unity-related run configurations got new icons.
  • Unknown project reference error is disabled in .asmdef files.
  • A solid bugfix update.
  • Other:
  • The plugin Visual Studio Team Services has been updated with lots of fixes.

New in Rider 2018.2 Build 182.3944.254 EAP 6 (Aug 4, 2018)

  • F# SUPPORT:
  • F# File Templates have been introduced.
  • FSharp.Compiler.Service has been updated to receive F# 4.5 features/changes, the most notable of which are: Span support and match! keyword.
  • The interop with C# projects has been improved, including the following F# 4.1 features:
  • Struct annotations for Records and Unions.
  • Implicit Module suffix.
  • UNITY SUPPORT:
  • Rider does not crash Unity 5.6.x versions anymore.

New in Rider 2018.1.4 Build 181.5550.7 (Aug 3, 2018)

  • Bug fix update is here to fix an annoying issue with Rider requiring frequent restarts due to a hanging UI.

New in Rider 2018.2 Build 182.3797.86 EAP 4 (Jul 20, 2018)

  • dotCover is finally here! Continuous testing, unit test code coverage analysis, and code highlighting are available for you to preview and play with.
  • Unity:
  • Support for debugging remote players has been improved.
  • "Attach and play" run configurations have been updated.
  • Debugger:
  • The Watches window now offers code completion, typing assistance, code highlighting, and other neat code insight features.
  • C# Interactive:
  • Code completion, typing assistance, and code highlighting are now available for C# Interactive.
  • NuGet:
  • We’ve introduced initial support for MSBuild-based restore.
  • Other:
  • Scratch Files now supports most of the features available for standard C# files.
  • See also: more fixes in this build at:
  • https://youtrack.jetbrains.com/oauth?state=/issues?q=in:Rider%20%23Fixed%20%23Verified%20Fix%20versions:%202018.2

New in Rider 2018.2 Build 182.3624.343 EAP 3 (Jul 15, 2018)

  • Publish support:
  • Only publishing of ASP.NET Core Web projects is supported.
  • There are two new run configurations, Publish to IIS and Publish to custom server.
  • Publish to IIS can deploy a web application to a local or remote IIS or Kudu (Azure Web Apps), or create
  • an MSDeploy package (MsDeploy is only supported on Windows). It uses .pubxml configuration files.
  • Publish to custom server supports FTP and FTPS/SFTP. This is available on Windows, Mac OS X, and Linux.
  • Template editor:
  • Live/Surround templates can be configured under Editor | Live Templates.
  • File templates can be configured under Editor | File Templates.
  • Creating multifile templates is not yet supported.
  • Debugger:
  • Docker support has reached the debugger. There are some limitations for now: it covers only .NET Core,
  • only Linux containers, and only Dockerfile configurations (there's no docker-compose support yet).
  • We've added thread-specific breakpoints.
  • Unity support:
  • There's a new warning on usages of slow Camera.main in frequently called methods.
  • Code analysis correctly recognizes custom serializable classes and serialized fields, and their usages.
  • The Attach to Unity Process list now shows Unity players.
  • The Attach to Unity Process action has been added to the Unity actions drop-down in the toolbar.
  • Other updates:
  • A new Generate GUID action is available.
  • The Build settings icon is available on the toolbar in the Build tool window, leading you to
  • the settings page Build, Execution, Deployment | Toolset and Build.
  • A Runtime arguments field has been added to .NET-related templates on Run/Debug Configuration
  • for passing custom parameters to runtime.

New in Rider 2018.2 Build 182.3458.490 EAP 2 (Jul 10, 2018)

  • Unity support:
  • Mark potential event handler methods (and property setters) as ˜in use'.
  • A couple of new Live Templates were added: sprop and sfield.
  • Support for .asmdef files: JSON schema validation, code completion, Find Usages, Rename refactoring,
  • Navigation on references elements, AsmDef file templates, and inspections/quick-fixes
  • for self-reference and file name/assembly name mismatch.
  • Fix for the invalid warning for this == null in Unity types.
  • Removed a highlighted background by default for Cg blocks in ShaderLab files.
  • A settings page for ShaderLab color scheme was added.
  • ShaderLab keywords are correctly highlighted again; the correct connectivity icons are shown when
  • Unity is playing; and the Find in Text option on the Rename dialog is limited to comments and string
  • literals only in ShaderLab files.
  • We've added an option to disable Unity Reload Assembles when Unity receives focus in Play mode
  • (only for Unity prior to 2018.2, as 2018.2 has the same option natively).
  • Now the Editor plugin will only write project files if they've changed (Unity 2017.4+).
  • Other changes:
  • "Custom tools" can now be specified for a file extension in Settings.
  • Stack frames are better presented in the debugger as you can now restore async function's name and its types.
  • Types in the Memory View window are now formatted in C# style instead of the CLR style.

New in Rider 2018.1.3 Build 181.4952.311 (Jul 6, 2018)

  • Hot fix for the Zip Slip vulnerability.

New in Rider 2018.2 Build 182.3458.147 EAP (Jul 3, 2018)

  • Unity support: Open Unity Editor/Player log, new inspections and context actions, and more.
  • Unit Testing: Performance improvements, lock/unlock session, run and debug tests on Mono on Windows, and more.
  • Solution Explorer redesigned: New tree and toolbar design, new Folders Always On Top mode, merged Scratch View, and more.
  • NuGet: Support for TLS-1.2-only NuGet feeds and AutoReferenced packages, and filter and format customization in NuGet logs.
  • C# Interactive: Attach the debugger, and add project and assembly references to the current session.
  • Code Completion: New scoring engine, new code completion for pointers in unsafe context, and an active hotspot after
  • expanding a live template.
  • Debugger: Partially improved presentation of stack frames, support for Debugger.NotifyOfCrossThreadDependency,
  • changing debugger settings on-the-fly and inspecting unsafe pointers on Mono/Unity.
  • The re-run action is now available on the Find Usages tab.
  • Borrowed from ReSharper: out-of-the-box ReSpeller, partial C# 7.3 support, initial Blazor support, and more.
  • Inherited from IntelliJ IDEA and WebStorm: new icons, Version Control update, and updated support for
  • TypeScript/Angular/React/etc.
  • Please visit our blog for more information at:
  • https://blog.jetbrains.com/dotnet/2018/07/02/rider-2018-2-early-access-program-open/

New in Rider 2018.1.2 Build 181.4952.297 (Jun 1, 2018)

  • Hot fix update for smoother typing and completion.

New in Rider 2018.1.1 Build 181.4952.276 (May 26, 2018)

  • .NET Core 2.1, fixed deployment of Xamarin projects, loads of fixes for Unity, improvements for F# including debug in F# Interactive, and more.
  • Bug:
  • RIDER-5225 — Problem with paths in DotNetCoreRuntime
  • RIDER-8352 — Realm doesn't work
  • RIDER-8427 — Working with multiple .net core versions
  • RIDER-8689 — Android project created by Rider can not be deployed under VS 2017
  • RIDER-9761 — Cannot build R# plugin using dotnet build and netstandard2.0 due to references to .net framework assemblies
  • RIDER-10078 — [Params method invocation] Not evaluating expression in debug
  • RIDER-10411 — Low dpi icons
  • RIDER-10422 — Wrong icon for disabled daemon indicator (i.e. decompiled sources)
  • RIDER-10425 — Unnecessary border in Unit Test session dialog
  • RIDER-12410 — Useless extra border in UT tool window
  • RIDER-12578 — Unable to set the "encapsulate field" hotkey
  • RIDER-12677 — No way to change the column size in settings
  • RIDER-13097 — Rider forgets location of Android SDK with every launch
  • RIDER-13150 — Rider doesn't find "Trace Scenarios", "Browse Special Files and Folder" and "Contact Support" actions
  • RIDER-13160 — Default Evaluate expression window size
  • RIDER-13469 — Use default error color in Xamarin.Android settings
  • RIDER-13576 — Step over doesn't move to the next statement in this block
  • RIDER-13693 — Rider drops Android ndk on solution open
  • RIDER-13762 — Cannot run unit tests with .Net Core and Paket
  • RIDER-13865 — Cannot change Android default deployment target
  • RIDER-13940 — Static Analysis w/ C# consuming F# "Cannot access private constructor"
  • RIDER-13988 — stepping through breakpoint debugger takes multiple keypresses
  • RIDER-14278 — Annotations source code -> "Copy C# implementation to clipboard" doesn't work on Mac/Linux
  • RIDER-14326 — Hard to press `run` gutter mark due to irrelevant break point suggestion
  • RIDER-14566 — Roslyn analyzers ignore toolset
  • RIDER-14627 — There is no gutter mark for 'Find implementations'
  • RIDER-14756 — Add more file extensions to Cg category
  • RIDER-14880 — Verify that Rider works with Entity Framework 6.0... 6.1.3
  • RIDER-14956 — Unity log viewer doesn't parse relative file names on Mac
  • RIDER-14973 — Debugger doesn't work in WinForms constructors
  • RIDER-14986 — Entity Framework Force Migration Create a Duplicate file
  • RIDER-14991 — Ef Add-Migration Configuration Project is incorrect
  • RIDER-15017 — When User Add-Migration, Rider don't open migration file.
  • RIDER-15033 — 'cannot resolve symbol' does not work properly
  • RIDER-15073 — Roslyn Analyzers shouldn't analyze unloaded projects
  • RIDER-15075 — Provide a popup menu for Roslyn icon in the status bar
  • RIDER-15077 — Show user-friendly message about errors in Roslyn Analyzers
  • RIDER-15078 — Cannot run Xamarin iOS app, "Select deployment target" and "Update Codesign Key" dialog item doesn't get focus
  • RIDER-15079 — Don't tell me about Roslyn analyzers if they don't affect my solution
  • RIDER-15081 — Rider hangs on Debug.Log on every Update
  • RIDER-15087 — Roslyn analyzer icon with progress and error indicators looks strange
  • RIDER-15093 — References in mcs.rsp interpreted differently from how Unity/Mono does it
  • RIDER-15113 — Incorrect error message on attempt to run ASP.NET project in environment without IIS.
  • RIDER-15114 — Nested exception types cannot be muted
  • RIDER-15118 — Cannot move exception popup
  • RIDER-15144 — This site can’t be reached on asp.net core mvc template (2.1.300-preview2-008530 sdk)
  • RIDER-15168 — Autocomplete interprets space key as an acceptance of variable new name instead of rejection, while existing variables will not complete at all
  • RIDER-15179 — Failed to shadow copy output in XAML Preview (wrong message)
  • RIDER-15182 — Download link on Linux for .NET Platform templates should navigate to mono-develop project (or just show hint "sudo apt install mono-devel"), currently it navigate s to ms site
  • RIDER-15197 — XAML Preview not available
  • RIDER-15204 — Show instances always applied to the container class
  • RIDER-15215 — Detect ASP .NET URLS from launchSettings.json
  • RIDER-15217 — Unity: asmdef file changes are not picked up by Rider
  • RIDER-15230 — windowsAuthentication enabled True not being saved when added to a C# Project through GUI
  • RIDER-15255 — Alt+Enter with debugger actions doesn't work at all in ext sources
  • RIDER-15260 — Tiny status circle should be red, if there are red tests in currently running session
  • RIDER-15320 — Moving folder via drag'n'drop not working
  • RIDER-15321 — Rider is deleting Default run-configuration when adding reference to UnityEngine.dll
  • RIDER-15355 — Rider run/debug window does not wait for ReadLine
  • RIDER-15356 — Escape action is broken on welcome screen
  • RIDER-15387 — Autocomplete is active in literal text in Razor code
  • RIDER-15397 — XAML Preview can't find static resrouce if it was registred in App.Xaml as application resource.
  • RIDER-15419 — 2018.1 — Xamarin.iOS, cannot deploy
  • RIDER-15446 — Unable to run any Unit tests
  • RIDER-15480 — Parallel Stacks is not available on first stop of debugger
  • RIDER-15514 — Unable to deploy Xamarin.iOS or Xamarin.Android projects
  • RIDER-15522 — Unity logs in Rider are only displayed, if UnityEngine.Debug.Log was called from the main thread.
  • RIDER-15524 — StackOverflow when loading F# project
  • RIDER-15577 — Renaming class (and file) while Unity Explorer is open has strange result
  • RIDER-15602 — Interactive c# not working on Mac with latest Mono
  • RIDER-15676 — Initial setup action hangs when I run it with empty App.config file
  • RIDER-15722 — Debugger "Could Not Evaluate The Value" This happens with all values
  • RIDER-15738 — Unity crashes in the background while typing in Rider
  • RIDER-15741 — Backslash changed to forward slash in run configurations
  • RIDER-15769 — Incorrect Migration file with nested class
  • RIDER-15809 — Can't run unit tests (pong-tdd)
  • RIDER-15849 — Difference between test id in Rider and nunit
  • RIDER-15855 — Project with missing imports can not be loaded
  • RIDER-15872 — Unable to insert breakpoint inside cshtml files
  • RIDER-15879 — Database tool window disappears
  • RIDER-15881 — Cannot detect dbgshim path for execute path
  • RIDER-15909 — Rider freezes while running unity project
  • RIDER-15947 — Parallel stacks merges threads based only on method name
  • RIDER-15955 — Native executable run configuration: cannot pass more then one program argument
  • RIDER-15974 — "Project load finished with warnings: Assets file not found" on opening .net core templates
  • RIDER-15991 — Registered Patterns does not work for Shaderlab & Cg when adding *.hlsl (for Unity 2018)
  • RIDER-16001 — Rider opens http://localhost:5000/ in a browser each time i run project
  • RIDER-16043 — Problem with NuGet in Orchard solution
  • RIDER-16072 — Attach to Unity dialog doesn't help selecting executable
  • RIDER-16092 — JetBrains.Resharper.Host CPU load 100%
  • RIDER-16180 — Cannot change configuration project for EF to look for connection string, or provide a connection string manually.
  • RIDER-16184 — SolutionBuilder on Mono should always use 1sec-resolution for GetLastWriteTime
  • Configuration Problem:
  • RIDER-15934 — Jetbrains Rider 2018.1 doesn't find Console namespaces (PS4, Nintendo Switch etc) in Unity 2017.4.1f1
  • Cosmetics:
  • RIDER-14598 — Wrong size of NewSolutionFolderDialog
  • Exception:
  • RIDER-3746 — Failed to evaluate the data rule. Range is out of document range
  • RIDER-11605 — KotlinNullPointerException: Catch
  • RIDER-13449 — AssertionError: Assertion failed
  • RIDER-14272 — ObjectNotDisposedException: Editor of class com.intellij.openapi.editor.impl.EditorImpl hasn't been released:
  • RIDER-15068 — ObjectNotDisposedException: Editor of class com.intellij.openapi.editor.impl.EditorImpl hasn't been released:
  • RIDER-15070 — KotlinNullPointerException: Catch
  • RIDER-15177 — RdFault: All documents should be comitted, but some are dirty, reason: JetBrains.Util.Assertion+AssertionException: All documents should be comitted, but some are dirty at JetBrains.Util.Assert...
  • RIDER-15208 — Entity Framework throws exception after adding migration to project
  • RIDER-15431 — PluginException: Icon cannot be found in '/rider/actions/menu-openSolution.png', action 'class com.jetbrains.rider.projectView.actions.openExisting.RiderOpenSolutionAction' [Plugin: com.intellij]
  • RIDER-15438 — PluginException: Icon cannot be found in '/rider/actions/previousOccurence.png', action 'class com.jetbrains.rider.solutionAnalysis.actions.SWEAPrevErrorAction' [Plugin: com.intellij]
  • RIDER-15882 — Newly added file (found in db) is already presented in map, id=101
  • RIDER-15898 — Value cannot be null. Parameter name: value
  • RIDER-15948 — The path is not a valid file system path because it is not absolute, and only an absolute path can be resolved into an actual file system object.
  • RIDER-15996 — PluginException: Icon cannot be found in '/rider/actions/menu-openSolution.png', action 'class com.jetbrains.rider.projectView.actions.openExisting.RiderOpenSolutionAction' [Plugin: com.intellij]
  • Feature:
  • RIDER-6795 — Support showing values inline in debugger for F#
  • RIDER-9174 — "start new line before current" command not working
  • RIDER-15361 — Embedded pdb support
  • RIDER-15410 — Read .NET Core SDK version from global.json
  • RIDER-15946 — NuGet - Support NTLM authentication (Windows)
  • Usability Problem:
  • RIDER-11557 — Provide icon for 'Run with Coverage'
  • RIDER-14327 — Add option for disabling breakpoint suggestion on mouse hover
  • RIDER-15016 — enum code completion isn't smart
  • RIDER-15061 — Highlight stacktraces in EF console and in Roslyn console

New in Rider 2018.1.1 Build 181.4952.203 EAP 1 (May 18, 2018)

  • HIGHLIGHTS:
  • Support for .NET Core 2.1 RC.
  • Fixed deployment of Xamarin projects.
  • Step Over works as expected and moves to the next statement in the block.
  • Fixed drag-and-drop to move folders in C# and VB projects;
  • Step and Refresh actions for Unity projects work correctly.
  • F# improvements:
  • Added inline debugger values;
  • Improved memory usage and performance in projects with multiple target frameworks.

New in Rider 2018.1 Build 181.4379.1191 (Apr 19, 2018)

  • Highlights:
  • Roslyn analyzers: in addition to Rider’s own 2400 code inspections to help you detect errors and code smells in all supported languages, Rider now detects Roslyn analyzers and highlights them in the code editor.
  • Entity Framework support: enable, add and get migrations, and update database with UI-based Entity Framework 6.x support in .NET Framework projects.
  • Deeper integration with Unity: this update takes Unity integration to a whole new level. Now you don’t even have to leave Rider to control Play mode, explore Unity logs, or run Unity-specific tests.
  • XAML preview: WPF application developers can now preview UI as they make changes to XAML code.
  • Memory view in debugger: Rider allows you to look under the hood of any application and explore the managed heap while debugging.
  • Exception pop-up, which shows summary of exceptions that occur while debugging and allows you to quickly navigate through the highlighted stack traces.
  • Even more debugger improvements including Smart Step combined with Jump to Statement, symbol server support, Attach UI that contains process info and suggests elevating permissions if necessary, faster attaching to local processes, and more.
  • NuGet updates: improved support for authenticating against private NuGet feeds in several ways, and initial support for bulk operations.
  • JetBrains redistributable of MSBuild to develop and build full .NET Framework applications without a Visual Studio or Visual Studio Build Tools installation on Windows.
  • Better understanding of projects and solutions: full support for Web References and Web Site projects, and more.
  • F# support brings file ordering and improves F# scripting in many ways, including code completion, highlighting and navigation.
  • Changes from ReSharper 2018.1: full understanding of C# 7.2 and improved support for previous C# versions, inspections and quick-fixes for formatting problems.
  • More frontend features: support for the latest TypeScript 2.7 features, handy updates for configuring package managers, improved Rename refactoring, better navigation in HTML files, and refined code completion.
  • Changes from IntelliJ IDEA 2018.1: support for multiple Docker Compose files, regex replacement preview in the Replace in Path dialog, a new lightweight documentation popup, and more.
  • VCS improvements: partial Git commits, new Group by icon to group local changes, and more.
  • More changes: a new MSTest setting dialog and customization settings for C# Interactive, Ideolog plugin available for download from the IDE, and more.

New in Rider 2018.1 Build 181.4379.974 EAP 8 (Apr 11, 2018)

  • Added support for Entity Framework 6.0 - 6.1.3.
  • Stabilization and bug fixes.

New in Rider 2018.1 Build 181.4379.788 EAP 7 (Apr 10, 2018)

  • Highlights:
  • Fixed support for Unity 4.7-5.5.
  • New MSTest test settings dialog: File | Settings | Build, Execution, Deployment | Unit Testing | MSTest.
  • Improved Code Completion for XAML.
  • More fixes in this build at:
  • https://youtrack.jetbrains.com/issues/RIDER?q=Fix versions: 2018.1 Fixed in Release: {2018.1 EAP 7} #resolved

New in Rider 2018.1 Build 181.4379.538 EAP 6 (Apr 4, 2018)

  • Highlights:
  • Roslyn analyzers support is enabled by default.
  • Nuget packages fine-tuned and more accurate modify projects while they're being set up, updated or removed.
  • Fixed false positives in code inspections for Razor Pages and projects targeting multiple frameworks.
  • More details about fixes in this build at:
  • https://youtrack.jetbrains.com/issues/RIDER?q=Fix versions: 2018.1 Fixed in Release: {2018.1 EAP 6} #resolved

New in Rider 2018.1 Build 181.4379.360 EAP 5 (Mar 31, 2018)

  • HIGHLIGHTS:
  • Memory view window for Debugger.
  • Initial support for NuGet bulk operations.
  • Sorting files in dependency order and drag-and-drop files reordering for F# projects in Solution Explorer.
  • Initial Entity Framework support (reachable under Tools | Entity Framework) that includes the following functionality:
  • Support for Entity Framework 6.2;
  • Enable Migrations, Add Migration, Get Migrations, Update Database, Initial Setup;
  • Smart code completion for fields in the dialogs filters the suggestions list and shows only applicable projects, types, and names.
  • More details about fixes in this build at:
  • https://youtrack.jetbrains.com/issues/RIDER?q=Fix versions: 2018.1 Fixed in Release: {2018.1 EAP 5} #resolved

New in Rider 2018.1 Build 181.4379.104 EAP 4 (Mar 27, 2018)

  • Highlights:
  • Added an ability to debug an application where elevation is required; elevated processes are displayed in the attach menu.
  • Improved UI for Unity Log tool window includes icons for actions and tooltips, as well as more readable output messages.
  • New icons and references folder for Unity Explorer.
  • New action allows removing project references from .csproj projects.
  • Scratches view is working as expected with a fully-fledged context menu.
  • More details fixes in this build are available at:
  • https://youtrack.jetbrains.com/issues/RIDER?q=Fix versions: 2018.1 Fixed in Release: {2018.1 EAP 4} #resolved

New in Rider 2018.1 Build 181.4035.533 EAP 3 (Mar 20, 2018)

  • Roslyn support provides syntax highlighting, quick-fixes, and context actions for your custom Roslyn analyzers: Editor | Inspection Settings | Roslyn Analyzers.
  • Support for Web References includes the ability to view web references in the Solution Explorer, discover and add WCF web references by URL, and remove existing web references.
  • Improved discovery and auto-detection of MsBuild.
  • Upgraded support for F# scripting:
  • Navigation commands such as Search Everywhere, Go to Symbol, Go to File Member, Find Usages, and Viewing File Structure, and as well as #load directives, all work correctly.
  • Smart Code Completion for files in directives provides all the applicable files from subdirectories and inserts the relative path.
  • Code Completion, highlighting, and analysis work as expected.
  • Unity enhancements:
  • Assets Refresh will not be called automatically if Auto Refresh is disabled in Unity. However, manual refresh is still possible from the IDE, even if Auto Refresh is disabled.
  • A status bar indicator shows whether Unity Editor is connected, refreshing, or in Play mode.
  • Unity and NUnit tests execute through Unity Editor.
  • More fixes in this build at:
  • https://youtrack.jetbrains.com/issues/RIDER?q=Fix versions: 2018.1 Fixed in Release: {2018.1 EAP 3} #resolved

New in Rider 2018.1 Build 181.4035.96 EAP 2 (Mar 7, 2018)

  • Run/Debug configuration for Web Site projects.
  • New customization settings for C# interactive: set focus tool window on open/Send Line, or move the caret down on Send Line (adjustable in Preferences | Language & Frameworks | C# Interactive).
  • Support for .NET Framework unit tests for the new type of csproj projects on Linux/macOS via Mono.
  • Unity improvements:
  • New Toggle Output Position and Use Soft Wraps options for the Unity logs tool window.
  • Unity logs cleans itself after every switch to Play mode.
  • Plugin installer works automatically as expected – no manual effort needed to download a new version.
  • Incorrectly applied attributes are highlighted in grey as a warning of redundant code, instead of showing an error.
  • Code inspections for Null-Coalescing and Null-propagating operators.
  • [PublicAPI] annotation now marks all class members (fields, properties, etc) as ‘in use’.
  • Added undocumented UIBehaviour APIs.

New in Rider 2018.1 Build 181.3782.222 EAP 1 (Feb 28, 2018)

  • MyGet and VSTS credential providers for private NuGet feeds.
  • Added the ability to edit project properties in .NET Core solutions.
  • Support for ProjectUISubcaption project properties.
  • Ideolog plugin is available for download from the IDE: Preferences | Plugins | Install JetBrains plugins...
  • Debugger enhancements:
  • Return value locals now contain text from the source code in the Debugger tool window.
  • The application’s embedded console in the Debugger tool window displays output more reliably (on Windows).
  • Use the Exception popup to explore exception details in a simplified way.
  • Attach window displays the process username (on Windows) and suggests elevating permissions.
  • Unity support improvements:
  • Unity logs tool window lets you explore the same logs from the Unity editor console with hyperlinked stack traces.
  • Unity Explorer structure view duplicates Unity’s view of assets.
  • The Game View actions (Play/Pause/Step/Stop) are available directly from Rider.
  • Thanks to the two-way communication, any changes applied in Rider in Edit mode will be instantly delivered to the Unity Editor.
  • Code completion, find usages, and usage highlighting are available for ShaderLab properties when used in Shader blocks.
  • Fixed ShaderLab color reference handling with non-US locales.
  • Support for the BaseDirectory project property.
  • Fixed issues:
  • RIDER-4545 — Enhance Attach to Local Process flow
  • RIDER-9684 — Edit project/file properties for .NET Core
  • RIDER-8243 — Add support for VSTS credential provider in NuGet client
  • RIDER-13596 — Exceptions are not shown when thrown in async methods
  • RIDER-6294 — Setting "Don't indent comments started at first column" does not appear to work
  • RIDER-12524 — The cell contents in Settings code style pages are invisible because the columns are too narrow.
  • RIDER-757 — Debugging IIS
  • RIDER-6050 — Rider doesn't show w3wp.exe in the list of executables available to attach the debugger to.
  • RIDER-12526 — Exception breakpoints hang the debugger when they happen in an async method
  • RIDER-1075 — Open MSDN pages on F1 or Shift-F1
  • RIDER-7299 — File properties not working in .NET Core projects
  • RIDER-7284 — Rider file colors stopped working
  • RIDER-8043 — Mark somehow references which were resolved but not to HintPath
  • RIDER-10055 — Support Unity/MonoDevelop's BaseDirectory csproj property
  • RIDER-10128 — Debugging opens external console when configured not to
  • RIDER-11361 — Attach to process should show username
  • RIDER-11981 — Don't add property group with $(Configuration)|$(Platform) to sdk-based csproj. Use `Configurations` and `Platforms` properties instead.
  • RIDER-12398 — Solution configuration is not saved if one of the projects failed to load
  • RIDER-12660 — Add the ability to place inline comments next to the code
  • RIDER-12723 — Second level folders don't show folder properties or Live Templates if BaseDirectory is set
  • RIDER-13190 — "Executing public with terminated lifetime" exception
  • RIDER-13563 — NullPointerException: null
  • RIDER-771 — Debugger and unhandled exception
  • RIDER-4016 — Exception while commit project level transaction: Cannot modify an evaluated object originating in an imported file "/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/xbuild/14.0/bin/Mic...
  • RIDER-4777 — Solution load failed after upgrading xunit to the latest version
  • RIDER-6577 — MacOS: custom layers are created without extension .DotSettings
  • RIDER-6867 — NugetSearcher.ZeroLatencyUpdate is called on solution close
  • RIDER-7128 — Load failed with custom path to MSBuild on Mac
  • RIDER-7869 — "Any CPU 32-bit preferred" setting is inactive
  • RIDER-7964 — Deleted project appears in the list of executable projects in the Run/Debug Configurations
  • RIDER-8569 — Got an error while playing with nugets
  • RIDER-9307 — Can't attach the debugger to another user process.
  • RIDER-9652 — Support element
  • RIDER-12696 — Destination array is not long enough to copy all the items in the collection. Check array index and length.
  • RIDER-10409 — Odd margin for the input field
  • RIDER-10662 — Switch Solution on opening file from Unity
  • RIDER-10682 — Include linked items doesn't work
  • RIDER-10752 — Test startup time is multiple MINUTES
  • RIDER-10862 — Mono executable not auto-detected
  • RIDER-11227 — add notifications if I have to update all necessary SDKs for Android and iOS (Xamarin related) before iOS deployment
  • RIDER-11318 — Platform path separators are used when creating a project from template
  • RIDER-11430 — "New solution" window can't be resized
  • RIDER-11433 — Build fails after switching to a branch which has a project removed
  • RIDER-11485 — Good Code is Red: ValueCollection of Dictionary
  • RIDER-11534 — Renaming folder via Solution Explorer does not change the project file
  • RIDER-11609 — Implement exception popup for all kinds of exceptions
  • RIDER-11632 — Out of memory
  • RIDER-11719 — Rider from Toolbox can't see IIS for debug!
  • RIDER-11969 — Smart step into not working while debugging unity
  • RIDER-12084 — Exception after highlighting inside unloaded project
  • RIDER-12089 — Fix unzip problem.
  • RIDER-12156 — parsing pdb file is failed under Mac OS
  • RIDER-12170 — Unit test failed with exception "Could not create per-user temp directory in system temp"
  • RIDER-12186 — XDT configuration transformation files not nested in UI
  • RIDER-12218 — Rider doesn't offer to choose a language for unknown file extensions
  • RIDER-12331 — Cannot run NUnit tests in 32bit process on Mac
  • RIDER-12345 — CopyToOutputDirectory does not work for some project file
  • RIDER-12375 — Split .NET exe and exe run configuration.
  • RIDER-12383 — Invalid msbuild project file if there is & in the path
  • RIDER-12603 — Symbol Caches fail miserably after rename
  • RIDER-12666 — Debugging NUnit tests starts with modified environment and hangs
  • RIDER-12722 — BaseDirectory not applied if editing the project file directly while solution open
  • RIDER-12770 — Single-line breakpoint bug
  • RIDER-12789 — "Error running 'Android Default': Should be a PTY based process" error appears on deploy of Android blank application.
  • RIDER-12791 — Write MSBuild path to output when build started.
  • RIDER-12820 — Red code when switch branch
  • RIDER-12845 — Could not build solution with ReSharper build if set environment variable VisualStudioVersion and Toolset has same parameter.
  • RIDER-12846 — Add progress for attaching to process (including Unity)
  • RIDER-12870 — Not correct property "Copy to output directory" in file.
  • RIDER-12884 — Project templates
  • RIDER-12892 — Find Text window does not set breakpoint in editor
  • RIDER-13074 — Rider host has unexpectedly exited
  • RIDER-13177 — adding additional TargetFramework version leads to attributes duplication in csproj (.net core)
  • RIDER-13192 — F# plugin does not work in 2018.1 EAP
  • RIDER-13243 — Wrong item presentation
  • RIDER-13264 — Annoying exceptions "Assertion failed"
  • RIDER-13270 — shlwapi.dll
  • RIDER-13351 — The wrong position is displayed after applying "SetNextStatement"
  • RIDER-13352 — C# Interactive can now use csi that ships with Mono 5.8.0+
  • RIDER-13393 — Editor of class com.intellij.openapi.editor.impl.EditorImpl hasn't been released
  • RIDER-13397 — NPE in SaveAllTracker
  • RIDER-13419 — Autocomplete with enter does not work
  • RIDER-13429 — Wrong doc comment highlighting
  • RIDER-13444 — Don't show messages about being unable to evaluate value is debugger's inlined tips
  • RIDER-13489 — IllegalStateException: Not initialized: BuildModel.buildModelReady.$.buildSession.$.activeProjectName
  • RIDER-13485 — Add way to pass custom parameters in Rider debugger agent args.
  • RIDER-13490 — KotlinNullPointerException: null
  • RIDER-13495 — IllegalStateException: Catch: Not initialized: null (Not initialized: null)
  • RIDER-13500 — Can't drag current execution line when debugging
  • RIDER-13552 — Rider doesn't stop on exception when exception class is nested
  • RIDER-13614 — The tree goes crazy in the Solution Explorer after updating
  • RIDER-13623 — PrivilegedActionException: null
  • RIDER-13636 — IllegalStateException: Not bound
  • RIDER-13643 — Return value not show in debug view when null
  • RIDER-13648 — Repack NuGet packages with change version for MS.
  • RIDER-13653 — Missed menu item
  • RIDER-13654 — "Virtual" keyword sometimes doesn't appear in intellisense depending on lambda definition

New in Rider 2017.3.1 Build 173.3994.2442 (Feb 7, 2018)

  • Among other things, in this update you will find:
  • RIDER-12503 — Fixed unexpected project loading errors.
  • RIDER-6714 — Fine-tuned syntax highlighting for XML documentation comments.
  • RIDER-3491 — Shortcut for Move Caret to Matching Brace working as expected.
  • RIDER-12420 — Shared run configurations are back in the solution-specific folder: ./idea/.idea.SolutionName/.idea.
  • A lot of fixes in Code Completion including glitches with the autopopup and a set of improvements in the UI;
  • This bug fix release has a few noticeable enhancements as well:
  • Rider debugger can now step into third-party code in Unity projects (and all other Mono-based projects too!).
  • RIDER-12319 — Improved auto-detection of Unity Mono runtime.
  • RIDER-8453 — Debugging on connected iOS devices in Xamarin.
  • RIDER-9343 — Preview of Find Usages in the text editor.
  • Bug:
  • RIDER-1193 — Autocomplete messes up when completing a property declaration.
  • RIDER-3491 — move caret to matching brace doesn't work
  • RIDER-4652 — Postfix template pop-up doesn't work (e.g. var, not)
  • RIDER-6714 — Problems with xml doc comments highlighting
  • RIDER-8140 — "Refactor This" popup only shows when clicking elsewhere
  • RIDER-8656 — Searching word 'Exception' in Rider settings doesn't find anything
  • RIDER-8723 — Find Usages does not work on record fields which are bind in record pattern
  • RIDER-9386 — When copying a xaml control the codebehind doesn't get renamed
  • RIDER-10609 — Refactoring windows are dynamically resized, hence they blink on appearence
  • RIDER-10923 — Deadlock in ensure/query writable
  • RIDER-11079 — Module System.Private.Xml should be referenced.
  • RIDER-11121 — References to Roslyn Analysers look weird in solution explorer
  • RIDER-11288 — Code completion disappearing while typing
  • RIDER-11303 — Renaming a local variable with Refactor->Rename causes the selected variable name to get mangled
  • RIDER-11310 — rider cant resolve this namespace/include dependency
  • RIDER-11570 — Debugger under cursor actions should be enabled only in valid scope
  • RIDER-11586 — Dose inject language function in javascript string templete get litmited?
  • RIDER-11602 — No vertical scroll in Export file, impossible to select all settings at once
  • RIDER-11946 — False positive action updates in context menu
  • RIDER-12039 — Breakpoints in external sources should indicate that their are disabled if the corresponding option is set
  • RIDER-12042 — "Invalid exe path:" after changing working dir
  • RIDER-12046 — Override completion with attribute splits access modifier
  • RIDER-12052 — MSBuild Error (builds via vscode and cli)
  • RIDER-12094 — Dragging execution point in debugger does not work on F# code
  • RIDER-12152 — Update of .designer.cs works incorrectly after .resx file rename
  • RIDER-12155 — If to decompile via Threads view the frame location and other info aren't updated
  • RIDER-12160 — It seems unnatural that template items are not added into VCS
  • RIDER-12202 — Two breakpoints could be set to one line
  • RIDER-12211 — Set next statement icon does not set to previous statement in xUnit test project
  • RIDER-12212 — Debugger is detached after timeout ~30 sec in xUnit test project
  • RIDER-12269 — Extra items are shown inside some projects in Solution Explorer
  • RIDER-12272 — Debugger ballon warnings and errors should also be added to Console tab
  • RIDER-12277 — Failed to connect in SoftDebuggerSession is not logged to backend
  • RIDER-12278 — Lets pass to frontend debugger OnConnectionError also type of exception, not only message
  • RIDER-12288 — IDEA usages are grouped only by file when moving Go To results to Find tool window.
  • RIDER-12296 — Success tests filter does not work for xUnit tests
  • RIDER-12307 — No code inspections in Shared project
  • RIDER-12319 — Autodetect Unity mono on linux since Unity 2017.3
  • RIDER-12330 — Rider cannot debug Xamarin Mac Full projects
  • RIDER-12349 — Find Results tool window is shown even if Rider doesn't find any usages
  • RIDER-12350 — When there's 1 usage, Find Usages on a declaration displays the Find Results tool window instead of navigating to the usage
  • RIDER-12354 — Find Results opens with selection on "Search target", leaves "Found usages" tree collapsed
  • RIDER-12360 — Smart Step Into pop-up shouldn't overlap the multi-line statement that it is invoked on
  • RIDER-12391 — Cannot resolve View in ASP.NET Core app (created with dotnet sdk 1.1.0)
  • RIDER-12396 — Blinking "Run unit tests" item in context menu
  • RIDER-12418 — Async Stack Frame missing in release configuration
  • RIDER-12420 — Rider 2017.3 doesn't see shared run configurations
  • RIDER-12423 — "Autoscroll to source" doesn't work for files which are not included to project (csproj)
  • RIDER-12436 — "Error: Project is not specified" for ASP.NET Core webapi project run configuration
  • RIDER-12466 — Unable to create new solution
  • RIDER-12467 — Most of Akka.NET xUnit tests do not appear in unit test explorer
  • RIDER-12468 — Arrangement of Attributes settings not stored
  • RIDER-12479 — Auto Completion is not working in razor page (cshtml) and improve razor support
  • RIDER-12503 — Errors on opening solution. Code highlight and other functions doesn't work
  • RIDER-12525 — No code highlighting for get; set; keywords in property declaration
  • RIDER-12526 — Exception breakpoints hang the debugger when they happen in an async method
  • RIDER-12538 — 2017.3 splash screen is low-resolution on retina display
  • RIDER-12600 — Neither surrounding nor overtyping selection with { work
  • RIDER-12601 — Rider 2017.3 nightly doesn't find private methods in search everywhere
  • RIDER-12604 — selected text not deleted when write '='
  • RIDER-12609 — Rider 2017.3 on Mac fails to load project
  • RIDER-12665 — Build failure of .NET Core project as soon as multiple target frameworks selected
  • RIDER-12673 — Bring back "Run cmd shell" option for projects
  • RIDER-12676 — Rider 2017.3 no longer finds unit tests
  • RIDER-12700 — "Bulk rename" dialog is always empty
  • RIDER-12745 — Context-specific completion items should be above generic ones like current context or nguid
  • RIDER-12757 — Exception in component ctor
  • RIDER-12768 — XMLDOC see tag autocomplete is a bit buggy, displays the window for only a single frame update, won't allow me to select anything.
  • RIDER-12782 — The intellsense auto-popup immediately disappears after popping up
  • RIDER-12788 — RESX auto-generation does not produce valid Designer code for PCL
  • RIDER-12810 — Customizing 'Project View Popup Menu' doesn't work for Rider
  • RIDER-12813 — Renaming a file and only changing the casing makes the file disappear
  • RIDER-12833 — comments and parentheses
  • RIDER-12850 — Tool windows disappears
  • RIDER-12853 — Missing autopopup when completing CSS inside Razor pages
  • RIDER-12857 — Add a file type for MSBuild task definitions
  • RIDER-12881 — The editor really doesn't like brackets
  • RIDER-12940 — Unity3DRider.cs output ArgumentException when running in CI build machine.
  • RIDER-12977 — Code alignment issue
  • RIDER-12985 — Xamarin Forms Project - Rider 2017.3 - .ProjectRootElement.Open' not found
  • RIDER-12987 — Code alignment issue
  • RIDER-13012 — Show number formatting suggestions in string.Format
  • RIDER-13013 — Code alignment bug
  • RIDER-13026 — Tried to create Xamarin macOS app, got cryptic error message
  • RIDER-13045 — Typing "from" in a string literal sometimes causes the literal to be erased
  • RIDER-13049 — Completion is broken after dot
  • RIDER-13056 — Completion commit erases `open` keyword
  • RIDER-13186 — Rider is stuck Cache processing
  • RIDER-13203 — Code alignment bug
  • RIDER-13205 — Code alignment bug
  • RIDER-13228 — Typing close-brace does not work in overwrite mode
  • RIDER-13380 — XDT transform menu no longer showing for Web.config file
  • RIDER-13382 — Create a new solution (Console Application) and add Microsoft.NET.Test.Sdk nuget package. Under Run/Debug configurations menu shows "Error: Project is not specified". Project field shows "No projects to run".
  • Cosmetics:
  • RIDER-4294 — Build output window width is too "narrow" (not the window width, but the text output)
  • Exception:
  • RIDER-10998 — AssertionError: There are two CalcThreads running before one of them was cancelled
  • RIDER-12199 — Exception when start debugging for Microsoft.NETCore.App with not existing platform version
  • RIDER-12244 — Exception in debugger process: Exception in GetAllChildren() Evaluation is not allowed: The thread is not at a GC-safe point --- EXCEPTION #1/2 [EvaluatorException] Message = “Evaluation is not...
  • RIDER-12248 — Exception in debugger process: Error while resolving expression: Value must be positive. Parameter name: count --- EXCEPTION #1/1 [LoggerException] Message = “ Error while resolving expressi...
  • RIDER-12374 — Expression Evaluation throws an exception when checking class members
  • RIDER-12381 — Exception after navigation to find usages result after unloading a project
  • RIDER-12387 — Refactor web app solution dependencies cause exception
  • Feature:
  • RIDER-8453 — Enable Xamarin.iOS debugging on connected devices
  • RIDER-9343 — Rider does not show preview in "Find" window
  • RIDER-11034 — Go to class/symbol doesn't support showing results in toolwindow
  • RIDER-12110 — Open Full Test Output in Stack Trace Explorer disappeared
  • RIDER-12283 — Allow overriding showNotification of DotNetDebugProcess in derivatives of MonoConnectRemoteProfileState
  • Performance Problem:
  • RIDER-6870 — Do not synchronously call format for all project files
  • RIDER-12270 — myReadWriteLockAcquisitionForbidden == 0
  • Usability Problem:
  • RIDER-10056 — Rename "Strip trailing spaces" to "Trim trailing spaces" or create an alias for "Trim" in the search
  • RIDER-12574 — Unusable Generate popup
  • RIDER-13265 — Provide "OpenInBrowser" action in the SolutionExplorer context menu for html files

New in Rider 2017.3 Build 173.3994.1125 (Dec 27, 2017)

  • Highlights:
  • Debugging third-party code: you can now step through and set breakpoints in assemblies that Rider decompiles on-the-fly.
  • Smart Step Into: when you debug method chains or nested method calls, choose a particular call to step into, while stepping over all other calls in a line.
  • Return values in locals: function return values are displayed in the Variables view, which is useful when the result of a method call is not stored in a local variable.
  • More debugger improvements: debugger actions are available in the Alt+Enter menu, you can now drag-and-drop the execution pointer to an earlier or later location in code, and callers of async functions are now displayed in the Frames view.
  • New project wizard: Rider introduces a different grouping of project templates, allows creating repositories along with new solutions, and streamlines installing additional project templates.
  • Unit testing improvements, including new actions, local shortcuts, and more reliable filtering in the unit testing view.
  • C# Interactive tool window to execute C# statements without having to wait for compilation.
  • Unity support improvements, such as new context actions and code inspections, improved usability of code completion, and syntax highlighting in compute shaders.
  • Config transformations to modify settings in Web.config and App.config when packaging applications.
  • Reworked formatter: Rider learns to align code in columns, apply other new code styles, as well as disable or enable formatting for selected blocks of code.
  • More changes from ReSharper 2017.3, including a C# 7 ready Extract Method refactoring, more C# typing assists, and improved support for VB.NET.
  • More frontend features: notably, Rider bundles more IntelliJ platform plugins for frontend development (such as TSLint, CoffeeScript, Karma and Stylus).
  • Changes from IntelliJ IDEA 2017.3, including a new editor-based REST client, version control and database tooling updates, and a reworked Docker configuration system.
  • Performance improvements on loading and reloading projects, in debugger and code completion.
  • More changes related to NuGet and MSBuild support, keymaps, settings, and Find Usages.

New in Rider 2017.3 Build 173.3994.932 EAP 4 (Dec 20, 2017)

  • Resource.Designer.cs regenerates automatically after Resource.resx file is saved.
  • Unity support improvements:
  • Class library project template.
  • External documentation action displays a popup with Unity documentation.
  • Debugger enhancements:
  • Effortless debugging of third-party code.
  • Mono debugger supports lambda expressions as well as extension methods.
  • Accurate display of values for decimal, float, and double variable types.
  • Improved stack rendering performance.

New in Rider 2017.3 Build 173.3994.576 EAP 3 (Dec 14, 2017)

  • Improved Find Usages introduces new groupings; works asynchronously and instantly displays preliminary results of a search that is in progress.
  • Initial support for disabled package sources in NuGet packages.
  • Unity support improvements, including new context actions and code inspections.

New in Rider 2017.3 Build 172.4144.1873 EAP 1 (Nov 24, 2017)

  • Highlights:
  • New project templates.
  • Heaps of UI improvements in the Unit Tests window.
  • Many debugger enhancements such as Smart Step Into, async causality chain tracking, and support for dynamic modules/assemblies.
  • Performance improvements on loading and reloading solutions.
  • C# Interactive window.
  • Support for package references in classic .csproj projects.
  • Changes in settings: Export/import file, Reset and Copy settings to actions; Null Checking tab in C# code style settings; per-language separation on Inspection Severity configuration page.
  • Web.config transforms (XDT transforms).
  • Lots of improvements to support Unity.
  • Auto-open the namespaces during completion in F#.
  • Initial support for Value Tuples in VB.NET.
  • Updated code formatter, including new formatting options and fixes.
  • Improved Razor support.
  • C# 7 support extended with a code generation action that creates deconstructors from selected fields or properties.
  • New typing assists for multi-line comments and chained method calls in C#.
  • A fix for External Annotations support in .NET Core and .NET Standard projects.
  • More fixes in this build at:
  • https://youtrack.jetbrains.com/issues/RIDER?q=#Resolved Fixed in Release: {2017.3 EAP 1}

New in Rider 2017.2.1 Build 172.4144.1873 (Nov 13, 2017)

  • Rider bug fix update: Debugger improvements, less red code in Razor views on Mac, sweet new F# features and more.

New in Rider 2017.2 Build 172.4144.1459 (Oct 13, 2017)

  • .NET Core 2.0, MSTest, call and value tracking, open file or folder, F# and Unity support updates, and more.
  • .NET CORE 2.0:
  • Rider 2017.2 adds support for .NET Core 2.0 in addition to .NET Core 1.1.
  • All Rider's code inspections, navigation actions, quick-fixes and refactorings are now available for .NET Core 2.0. Rider can run and debug your .NET Core 2.0 projects, manage NuGet packages that are used in them, as well as run unit tests based on xUnit, NUnit or MSTest.
  • CALL AND VALUE TRACKING:
  • We've implemented some of the most insightful features that ReSharper has to offer: Call Tracking and Value Tracking.
  • Where does this value come from? Where is this value used? What are the call trees that this method is involved in? Using the new Inspect This action (Ctrl+Alt+Shift+A) in Rider, you can now figure this out. On member and parameter declarations, Call Tracking and Value Tracking actions are even directly available from the Alt+Enter menu.
  • Both features are currently available in C# and VB.NET.
  • MSTEST SUPPORT:
  • Rider's unit test runner already supported running and debugging xUnit and NUnit tests. With Rider 2017.2, based on popular demand, we are adding MSTest to the list of supported frameworks. This includes classic MSTest (a.k.a Visual Studio Testing Framework) as well as the emerging cross-platform MSTest V2.
  • MSTest V2 will work out of the box on Windows, Mac or Linux. As to classic MSTest, due to the way it's licensed, you need to have a Visual Studio instance installed on your machine in order to run classic MSTest-based tests in Rider. The path to Visual Studio needs to be configured in Rider settings under Build, Execution, Deployment | Unit Testing | MSTest.
  • OPEN FOLDER OR FILE:
  • Not all code is in a solution or project. With that in mind, we added a command to open an individual file or folder from the Rider start screen and the File | Open menu.
  • When you open a file or folder, you can use a lot of Rider features, including HTML/JavaScript/TypeScript support, version control, Go to File, Search Everywhere, as well as Find in Path.
  • ATTACH FOLDER TO SOLUTION:
  • Along with opening folders or files, Rider can now do something extra: attach any folder to a solution. This doesn't modify any project or solution files; instead, it simply makes the folder visible in Solution Explorer alongside your current solution.
  • This can be useful if you're working with a web application that has distinct frontend and backend parts, and they're maintained in separate repositories. In this case, attaching the frontend part to your .NET backend solution will let you edit both parts in Rider, without integrating the frontend into your solution structure.
  • PARALLEL STACKS, LAMBDA EVALUATION AND MORE DEBUGGER UPDATES:
  • The Debug tool window gets a new tab: Parallel Stacks. When debugging multithreaded applications, it lets us visualize the various threads that are active while debugging, as well as their call stack. Hovering over a thread displays all child threads. From the toolbar, you can jump to the active frame. Double-clicking an entry in the call stack will jump to source. And when stepping through code, the diagram will be updated depending on threads that are being started/joined.
  • Rider's debugger now lets you add lambda expressions as watches. The debugger will evaluate and execute the expression, visualizing the results.
  • When debugging applications that have lots of variables, you may want to mark variables with custom colors. This can now be done using the context menu or with a shortcut. Marking a variable makes it really easy to discover where it's used, for example in fields of other objects.
  • Finally, we enabled adding watches for nested items, such as properties of a property of an object, or an element in a collection.
  • NEW REFACTORINGS:
  • We keep adding more items from the broad set of refactorings originally available in ReSharper.
  • One of them is Transform Parameters. It lets you create a new class or struct and converts parameters of the selected method into encapsulated fields of the newly created type. After applying the refactoring, usages of parameters are converted into usages of properties of the type being created. This refactoring also allows getting rid of out parameters by introducing a tuple object return type.
  • Another new refactoring is Invert Boolean. It helps automatically invert a boolean member and transform true to false and rewrite all usages to invert the boolean logic.
  • CODE ANALYSIS UPDATES FROM RESHARPER 2017.2:
  • Rider 2017.2 comes with ReSharper 2017.2 as its engine for providing .NET support. This means a number of features announced with ReSharper 2017.2 are now available in Rider.
  • Examples include improved support for C# 7.0 (including pattern matching and out variables), and initial support for C# 7.1. Rider now supports the default literal, tuple projection initializers, async main and pattern matching with generics. Simply reference the latest compiler package and make sure to set the language level in your project file. By the way, Rider can also detect if language features from a higher language level are used, and provide a quick-fix to make a switch.
  • Rider also adds some new code inspections around IEnumerable, and will check XML documentation inheritance to make sure it is valid. This ensures documentation in the IDE as well as generated API documentation is correct.
  • EVOLVING F# SUPPORT:
  • Rider 2017.2 comes with a series of new features and improvements around F#.
  • For example, it's now possible to work with .NET Core F# projects, for both SDK 1.0 and 2.0. For F# projects that use Paket instead of NuGet, Rider now disables its automatic NuGet restore on loading such projects. This ensures that projects like Fable load properly in Rider.
  • We've addressed a set of issues that you faced working with mixed C# and F# code bases, ensuring that F# code is exposed correctly in C# projects.
  • Rider now enables code folding in the editor. Pretty much any multi-line expression/statement can now be folded or unfolded.
  • We've also implemented the Comment with Block Comment action, which comments out the current selection with (* and *).
  • Looking up the documentation never hurts when writing code, and Rider now displays XML doc comments in a tooltip when hovering over documented code.
  • When you debug, Rider now supports evaluating expressions on hover, allowing us to inspect a variable from within the editor.
  • UNITY DEVELOPMENT:
  • For game developers, we added support for debugging different Unity processes. You can now create a Mono Remote configuration to remotely debug standalone games, such as those running on an Android device. The IDE and debugger now also support working with modularized UnityEngine dll's.
  • In other notable Unity support news, we've significantly improved our ShaderLab parser, which results in better code highlighting in .cginc files and injected Cg fragments in .shader files. As an additional nice touch, Rider now highlights color values in ShaderLab files, and if you press Alt+Enter, you can modify the color using a color palette picker.
  • Generating Unity code is now easier, with file templates for new MonoBehaviour scripts, shaders and tests. Additionally, code completion and generation of event functions are now available in recent versions of Unity.
  • BETTER JAVASCRIPT AND TYPESCRIPT SUPPORT:
  • Courtesy of a newer version of bundled WebStorm, Rider 2017.2 now offers richer support for JavaScript and TypeScript:
  • When you hover over an object while holding Ctrl, the inferred type for the object is displayed in a tooltip.
  • Reworked JavaScript code style settings allow configuring how to order members of a class, such as constructors, fields and methods. To apply these settings, use the Code | Rearrange Code command.
  • When using CSS modules and importing them into a JavaScript file, Rider provides code completion and navigation support for class names in that module.
  • Rider now detects tsconfig.json and takes it into account when analyzing TypeScript files.
  • Code completion and navigation for Angular Material attributes is now available.
  • When using webpack, Rider better understands complex configurations and properly resolves paths in import statements and import suggestions.
  • VERSION CONTROL IMPROVEMENTS:
  • When you work with Git, Rider now lets you revert and reword local commits. To do this, use the context menu under the Log tab in the Version Control tool window.
  • From the settings under Version Control | Commit Dialog, you can now customize commit message rules and inspections. Do you put a blank line between the subject and the body? Should the maximum length of a commit message be defined? You can set these and similar rules. In addition, Rider provides quick-fixes for these rules, and reformatting code can also be done inside the commit message.
  • MAKE CHANGES FROM SEARCH RESULTS:
  • In Rider 2017.2, we improved the way you work with results of a textual search using Find in Path (Ctrl+Shift+F).
  • Search results from the same lines are now merged together. Also, the Preview pane now has a left-hand gutter that displays line numbers, navigation icons, context actions and local change markers. This makes it easy to make small changes directly from a search!
  • MORE UNIT TESTING IMPROVEMENTS:
  • There's more than MSTest support in terms of unit testing in this release. Here's a few more highlights:
  • NUnit tests are now supported for full .NET Framework, .NET Core 2.0, and .NET Core 1.1.
  • All unit test providers now have their own settings pages where framework-specific settings can be tweaked. In addition, it's possible to disable frameworks that are not in use.
  • We've also made performance improvements for solutions that contain large test sets, as well as tests that produce a lot of output (including word wrap).
  • NUGET UPDATES:
  • A number of updates went into Rider's NuGet client. We're now using NuGet 4.3 under the hood, which brings full support for SemVer2 and .NET Core 2.0. Rider adds support for wildcard versions in package references, too.
  • When referencing packages that are not targeting .NET Core 2.0 (but are known to work with it), the AssetTargetFallback property can be used to define "fallback" target frameworks for project's dependencies. By default, .NET Core 2.0 projects will have this property set to net461, meaning that any NuGet package that is compatible with .NET Framework 4.6.1 or higher can be used without additional configuration. Rider now also includes initial support for this.
  • You can now install CLI tools packages right from within the NuGet client, without manually editing the .csproj file. For example, this is useful with Entity Framework Core's database migration commands from Microsoft.EntityFrameworkCore.Tools.DotNet.
  • We made some UI changes as well: for example, you can now toggle position of the package details pane, which is useful if you prefer to keep the NuGet tool window vertically oriented. And when possible, package icons will be rendered in high DPI making everything look more crisp.
  • EVEN MORE CHANGES:
  • Here's a short list of other notable changes in this Rider release:
  • More and better code completion suggestions in CSS, JavaScript, TypeScript, .config, .csproj and XML files.
  • Improved Multi-line completion: for instance, import completion in C# is now available when you invoke code completion with multiple text carets set.
  • When generating code, such as overriding or missing members, Rider now shows descriptions of base members that are being overridden or implemented.
  • Import and export of all global settings is available, including both settings coming from ReSharper and the IntelliJ platform.
  • Solution-wide analysis (SWEA) is automatically paused during NuGet restore when running it doesn't make a lot of sense.

New in Rider 2017.2 Build 172.4144.808 EAP 3 (Sep 30, 2017)

  • Highlights:
  • Better npm integration: Rider opens the npm tool window and offers to run npm install on opening a solution that contains a top-level package.json files.
  • tsconfig.json is now detected and taken into account when analyzing TypeScript files.
  • Call Tracking and Value Tracking actions are now directly available from the Alt+Enter menu on member and parameter declarations.
  • Import and export of all global settings, including those coming from ReSharper and the IntelliJ platform.
  • Solution-wide analysis (SWEA) is automatically paused during NuGet restore.
  • Improved Unity support, including better highlighting in .cginc files and injected Cg fragments in .shader files.
  • Better presentation of paths to MSBuild, Mono and .NET Core in Rider settings (Build, Execution, Deployment | Toolset and Build).
  • Performance stabilization in progress.
  • Bug:
  • RIDER-3459 — It is impossible to set more than one breakpoint on the same line
  • RIDER-4698 — No "await" keyword suggestion on expression-body async methods
  • RIDER-4960 — There is [rider module] in inspection scope
  • RIDER-5933 — In debug mode expression is not evaluated
  • RIDER-6021 — Intellisense and code analysis doesn't work for dotnet core f# projects
  • RIDER-6096 — "Undo null?" popups show up when redoing changes in project model
  • RIDER-7048 — Code Format Import and Export settings broken
  • RIDER-7182 — No XML Doc in tooltips
  • RIDER-7519 — Cannot Undo after 'Move types into matching files' on solution level
  • RIDER-7523 — Cannot Undo after copy/cut-paste Class in solution explorer
  • RIDER-7525 — Redo doesn't work for any project model changes
  • RIDER-7843 — Typescript doesn't find the typings and shows "Correspoing file is not included in the tsconfig.json"
  • RIDER-7862 — Right Click on Project in Solution Explorer, Edit 'Project File.sln', new tab opens but it switches back to original tab that was opened.
  • RIDER-7890 — Duplicated tooltip for F# modules
  • RIDER-7926 — Pull Members Up does not obey selected target
  • RIDER-7986 — Let me see full path to xbuild/msbuild in UI somewhere, even if it is very long
  • RIDER-8067 — Unnecessary code completion for array indicies in VB.NET
  • RIDER-8069 — Wrong code completion for Get when creating Class Property
  • RIDER-8148 — Evaluate expression date operation
  • RIDER-8258 — Navigate To and Find Previous have same key bindings in Rider OSX
  • RIDER-8546 — 'Use Base Type' refactoring window works incorrectly
  • RIDER-8866 — F# scratch file should be script (fsx), not normal source file (fs)
  • RIDER-9116 — Can't build Angular/React templates
  • RIDER-9232 — Solution wide analysis doesn't support TypeScript discriminated unions
  • RIDER-9312 — Autocomplete occurs in literal text in Razor
  • RIDER-9364 — Nothing works on F# scratch files, an exception in the log
  • RIDER-9452 — Value Origin Presentation
  • RIDER-9484 — Exceptions are catched in my code only when are added in Stop on Exception...
  • RIDER-9485 — Go to definition and find usages do not work if symbol is defined in subnamespace in referenced project
  • RIDER-9580 — The result of "git diff" of .csproj files is sometimes almost useless
  • RIDER-9595 — Angular web app template has unresolved Views (red code) in it.
  • RIDER-9596 — New Angular app from template. No NPM tool window
  • RIDER-9611 — Multiline code completion for "class" deletes code
  • RIDER-9675 — Multiple entry point inspection should highlight all candidates
  • RIDER-9677 — Use different layers for error and warning
  • RIDER-9742 — TypeScript Service - typescript initialization error. Cannot read property 'createHash' of undefined
  • RIDER-9776 — Missing "Show in `Find Results`" button
  • RIDER-9777 — Rider is not picking up tsconfig.json
  • RIDER-9794 — F# plugin is absent in the latest nightly EAP
  • RIDER-9824 — After loading solution exception with "Cannot read scheme Unnamed3.xml: name is missed in the scheme data"
  • RIDER-9841 — Cannot choose a new name when renaming namespace
  • RIDER-9844 — Change Signature dialog for parameter value disables Next button after invalid value typed in edit box, even if radio button changed to something else
  • RIDER-9845 — Broken icons for .js and .json
  • RIDER-9849 — Go to File doesn't work with Folders
  • RIDER-9955 — 'Show diff' for *.csproj files highlights every line
  • Cosmetics:
  • RIDER-4873 — Don't suggest to expand a variable that has no children
  • Exception:
  • RIDER-9615 — NullPointerException: null
  • RIDER-9889 — Assertion failed: Project view pane not found: ProjectPane; subId:null; project: Project 'C:UsersRafaelDesktopgame makingDevBuildsThe ESG v1.3 [DevBuild]SourceCode' ProjectPlugins
  • Feature:
  • RIDER-7485 — VS Keymap: Alt + Num* for Show Next Statement (When Debugging)

New in Rider 2017.2 Build 172.4144.486 EAP 2 (Sep 23, 2017)

  • Highlights:
  • Call Tracking and Value Tracking, both available via the Inspect This menu.
  • VCS integration improvements.
  • JavaScript and TypeScript support improvements.
  • Open individual file or folder.
  • Attach folder to a solution.
  • Lambda expressions in debugger watches.
  • Auto-start or debug web applications.
  • Multi-line code completion.
  • Documentation displayed in code generation actions.
  • F# and Unity support improvements.

New in Rider 2017.2 Build 171.4456.3271 EAP 1 (Sep 5, 2017)

  • Support for .NET Core 2.0.
  • Debugger: Make Object ID, Parallel Stacks view, and basic support of Add to Watches on nested items.
  • New inspections, quick-fixes and context actions from ReSharper 2017.2 related to C# 7.0 and 7.1, IEnumerable usage analysis, and in XML documentation.
  • NuGet support improvements, including a client version upgrade (v4.3), complete semver2 support, understanding packages with wildcard versions etc.
  • Unity: improved debugging in different players, and support for modularized UnityEngine libraries.
  • New refactorings: Transform Parameters and Invert Boolean.
  • Redesigned navigation bar.
  • Fixes in F#/C# interop.
  • Unit testing:
  • (Classic) MSTest support (Windows only, requires a Visual Studio installation);
  • MSTest V2 (cross-platform);
  • xUnit in .NET Core 2.0 projects;
  • NUnit in .NET Core 1.1 and 2.0 projects;
  • Performance improvements in large solutions;
  • Support for tests with huge outputs.

New in Rider 2017.1.1 Build 171.4456.2813 (Aug 29, 2017)

  • This update improves debugging asynchronous code, avoids overwriting applicationhost.config files, adds a bunch of fixes around Xamarin.Android and Unity (including ShaderLab syntax support), bringing 50+ fixes in total.

New in Rider 2017.1 Build 171.4456.2169 (Aug 4, 2017)

  • Bug:
  • RIDER-2480 — Error: URI is not registered for csproj and target files
  • RIDER-3379 — Scaling issue with Wizard page
  • RIDER-4420 — IIS Express settings are ignored
  • RIDER-5642 — NullPointerException on startup
  • RIDER-5684 — Code Style Naming panel has broken labels
  • RIDER-5745 — make more relevant goto action result
  • RIDER-6387 — Inspection Settings options lack "Elements to skip" feature.
  • RIDER-6435 — F#: Provided types are not seen between F# projects
  • RIDER-6473 — F# single-case discriminated union's `Item` property is not seen in C# code
  • RIDER-6516 — Poor performance when editing large files on Mac OS
  • RIDER-6656 — Linux installer: bad aligning on Color Scheme choosing page.
  • RIDER-6847 — Constant 'rider action: updating indices...'
  • RIDER-6940 — Documentation comments are not collapsed by default even though the corresponding setting is on
  • RIDER-7057 — Change "loading" in Options to "loading..."
  • RIDER-7094 — Settings window is closed right after I open it from Welcome to Rider wizard
  • RIDER-7116 — Make edit-box for custom msbuild bigger
  • RIDER-7168 — Error loading .csproj
  • RIDER-7363 — Unit tests disappearing from explorer
  • RIDER-7470 — Fold regions
  • RIDER-7520 — 'Rider action': getting the action ready. Press Esc to cancel...
  • RIDER-7563 — Unit test action indicators do not appear for xUnit tests on F# files
  • RIDER-7616 — Project 'Assembly-CSharp' load failed: Unable to connect to MSBuild process
  • RIDER-7686 — C# editor does not respect `Optional` and `DefaultParameterValue` attributes
  • RIDER-7788 — Run and Debug sessions stop abruptly after 60 minutes
  • RIDER-7812 — Exception fields from F# are not visible in C#
  • RIDER-7813 — Optional method params from F# are required in C#
  • RIDER-7832 — There is a gap in the errors list in SWEA
  • RIDER-7834 — [design time only, build ok] Enum defined in F# is not accessible in C#
  • RIDER-7839 — Unreadable color font in wizard in Editor Color Schemes
  • RIDER-7842 — Entering brackets for type parameters leads to long editor hang
  • RIDER-7844 — No stack traces in exceptions on Ubuntu 16.04 for .net core project
  • RIDER-7866 — VS keymap does not apply
  • RIDER-7870 — Syntax highlighting is not updated until the caret moved anywhere
  • RIDER-7878 — Pressing escape doesn't terminate completion session
  • RIDER-7880 — After update to RC cannot load/build projects -> The reference assemblies for framework ".NETFramework,Version=v4.6.2" were not found.
  • RIDER-7891 — Jetbrains.Debugger.Worker.exe does not close and uses massive resources
  • RIDER-7897 — Rider keeps overwriting changes to applicationhost.config
  • RIDER-7907 — Debug doesn't work for self contained apps
  • RIDER-7928 — Project load failed
  • RIDER-7948 — F# class used from C# - 'the class X has no constructors defined'
  • RIDER-7951 — F# type with module of same name used from C# - errors imply module is referenced
  • RIDER-7989 — Analyze error: Cannot access internal enum '*' here
  • RIDER-8041 — Build errors *are not* shown incase a build fails while starting a debug session (F5). If you do a regular build (CTRL+SHIFT+B) they *are* shown.
  • RIDER-8206 — Working directory not found after changing .NET framework version
  • RIDER-8275 — Constructor of a class defined in F# code is not seen in C# code
  • Exception:
  • RIDER-4570 — "Remove unused references" throws exceptions
  • RIDER-4788 — IncorrectOperationException: Must not modify PSI inside save listener
  • RIDER-5397 — AssertionError: Isolated exception: All intentions must be filtered out. (All intentions must be filtered out.)
  • RIDER-7695 — TypeCastException: null cannot be cast to non-null type com.intellij.openapi.editor.ex.EditorEx
  • RIDER-7991 — IllegalStateException: Value com.jetbrains.rider.framework.MessageBroker$Subscription@26d5de82 already exist for key StaticEntity/1084
  • Task:
  • RIDER-5992 — F# support on Linux: absence of F# installation
  • Usability Problem:
  • RIDER-7853 — Add links to support to Rider Help

New in Rider 2017.1 Build 171.4456.1432 RC (Jul 15, 2017)

  • Highlights:
  • More performance improvements in terms of solution load, NuGet Restore, solution-wide analysis etc.
  • Extract Members to Partial refactoring and more refactoring improvements.
  • NuGet private feed authentication.
  • Debugger starts to support generics, extension methods.
  • Auto-inserting closing statements in VB.NET.
  • ShaderLab support in Unity plugin.
  • More consistency in web development features.
  • Per-file code analysis highlighting level configuration.
  • An option to use external console in run/debug configurations.
  • Bug:
  • RIDER-637 — Support other file types when adding new item
  • RIDER-945 — NuGet authorization support
  • RIDER-2467 — The Evaluate Expression debugging tool should support extension methods
  • RIDER-3980 — IDEA inspection on excluded file show up in status bar (SWEA), and doesn't show up in Errors in Solution view
  • RIDER-4160 — External console flag don't work for .NET Core.
  • RIDER-4255 — Keyboard shortcut fails to select all public methods on Extract Interface
  • RIDER-4607 — Rider restores .NET Core packages every time it starts
  • RIDER-4983 — No automatic 'End Sub' for VB
  • RIDER-5167 — Folder completion in "Move to Folder" doesn't work
  • RIDER-5237 — Evaluate expression isn't working for tons of reasons
  • RIDER-5277 — Javascript: undefined, window and other standard elements are undefined
  • RIDER-5547 — Rider debugger variables pane shows variable as null when it definitely is not null
  • RIDER-5551 — Rider Daemon is suspended
  • RIDER-5612 — Program 'MvcApplication.dll' does not contain a static 'Main' method suitable for an entry point
  • RIDER-5620 — NuGet restore doesn't work after toolset changing
  • RIDER-5729 — QF "Evaluate expression" crashes Rider on MacOS
  • RIDER-5783 — Inspection profiles: set focus on current inspection
  • RIDER-5848 — 'Highlighting level' slider doesn't affect anything
  • RIDER-5853 — Rider calls Base Classes for Super Types
  • RIDER-5877 — Usings Section Collapses Even When Caret Is Inside
  • RIDER-6005 — When I click on the Build button, the build tool window hides
  • RIDER-6157 — Add controller to .Net Core project
  • RIDER-6193 — Starting a build closes the build progress console window
  • RIDER-6273 — Rider daemon is disabled
  • RIDER-6276 — F#: Nothing works on just created Console application
  • RIDER-6330 — "File.cs not found among the loaded symbol documents" when trying to debug
  • RIDER-6342 — Rework context menu on the status indicator
  • RIDER-6346 — Run UT is available everywhere in Solution Explorer
  • RIDER-6445 — Editor Colors & Fonts are not applying
  • RIDER-6458 — Missing file template: .resx file
  • RIDER-6677 — Rider fails to build when dependency has ILMerged dependency
  • RIDER-6770 — "add reference" doesn't work for core projects
  • RIDER-6937 — Make a notification in case if dotnet 4.5 Developer Pack is not installed.
  • RIDER-6954 — Rider doesn't support external libraries
  • RIDER-7169 — Build doesn't work: can't receive project finished event
  • RIDER-7180 — Incorrect calculations on Variables screen
  • RIDER-7199 — No icon for File
  • RIDER-7290 — Key assigned for "Back" in key map does not go back
  • RIDER-7315 — Configure inspections level not working
  • RIDER-7368 — Todos in js files are not highlighted
  • RIDER-7412 — Code cleanup profiles: wrong options page is opened
  • RIDER-7430 — Refactor This is available on navigation bar items although all its containing actions are not available (or don't make sense)
  • RIDER-7437 — Empty cleanup profiles page in settings opened from Welcome Screen
  • RIDER-7465 — VS Keymap: Ctrl+O
  • RIDER-7474 — Opening a solution triggers a full package restore
  • RIDER-7480 — Injected code fragment background highlight not working
  • RIDER-7492 — Primitive standard types not resolved in TypeScript
  • RIDER-7506 — Duplicated class after 'Move To Another File'
  • RIDER-7553 — Templates should reference FSharp.Core.dll via the NuGet package instead of using GAC
  • RIDER-7556 — IllegalArgumentException: Parameter specified as non-null is null: method com.jetbrains.resharper.settings.RiderSettingsDialogFactory.create, parameter project
  • RIDER-7558 — Rider hangs forever, ReSharper host consumes a lot of CPU
  • RIDER-7573 — Different examples and bad layout in Keymaps
  • RIDER-7576 — Multiple compile errors or typing parenthesis crash the Rider application
  • RIDER-7597 — Moving an inherited class to another file instead deletes the file in specific instance
  • RIDER-7606 — (has missing packages) message in solution explorer when targeting full framework
  • RIDER-7620 — "File" command has no glyph on the toolbar
  • RIDER-7631 — Yellow bar in unit test tool window on hi-DPI
  • RIDER-7649 — Working Directory in Run/Debug Configuration not saved or loaded.
  • RIDER-7651 — Rider modifies csproj with bin/obj folders and deletes spaces and splits lines with comments
  • RIDER-7661 — "Declaration: getting the action ready" tooltip appears all the time after changing F# file
  • RIDER-7663 — Navigate to symbol runs forever, no CPU load
  • RIDER-7680 — Getting exception when try to use TypeScript 2.4.1 installed in project folder.
  • RIDER-7681 — NuGet package install timeout
  • RIDER-7719 — Can not debug .net core msbuild task anymore
  • RIDER-7787 — No action bar in 'manage layers' dialog
  • RIDER-7816 — Report posting failed: java.net.SocketTimeoutException: Read timed out.
  • Cosmetics:
  • RIDER-6875 — Strange characters on Console.ReadLine()
  • Exception:
  • RIDER-5602 — Exception in debugger process: Exception in GetExpressionValue() Attempted to divide by zero. --- EXCEPTION #1/2 [DivideByZeroException] Message = “Attempted to divide by zero.” ExceptionPath = Ro...
  • RIDER-6743 — Element JetBrains.ReSharper.Psi.CSharp.Impl.Tree.Whitespace is not valid.
  • RIDER-6982 — Component descriptor JetBrains.ReSharper.Psi.FSharp.Searching.FSharpSearcherFactory [Singleton, Corrupted] is corrupted and cannot be accessed
  • RIDER-6983 — Create language definition JetBrains.ReSharper.Psi.FSharp.FSharpLanguage Language JetBrains.ReSharper.Psi.FSharp.ILanguageFSharpZone does not have static public fields declaring instance
  • RIDER-6984 — Component descriptor JetBrains.ReSharper.Psi.FSharp.Searching.FSharpSearcherFactory [Singleton, Corrupted] is corrupted and cannot be accessed
  • RIDER-7098 — Option isn't editable
  • RIDER-7161 — Action with id 'ExtractClass' not found.
  • RIDER-7455 — PrivilegedActionException: null
  • RIDER-7530 — Assertion failed
  • RIDER-7664 — User mono runtime is not specified and can't be discovered. Using Rider internal runtime instead
  • RIDER-7667 — The Reentarncy Guard deferred actions queue on thread :1 has reached the size of 8,193 items.
  • RIDER-7705 — The folder already exists
  • RIDER-7714 — Project /home/botsman/RiderProjects/Library/Library/Library.fsproj is not opened
  • RIDER-7799 — KotlinNullPointerException: Isolated exception: SolutionModel.solutions.[1].nuGetHost.configManager.ultraConfig
  • RIDER-7802 — IndexOutOfBoundsException: null
  • Feature:
  • RIDER-2412 — Missing code cleanup from Resharper
  • RIDER-7486 — VS Keymap: Ctrl+Shift+F10 for Set Next Statement (When Debugging)
  • RIDER-7518 — VS Keymap: Ctrl+Alt+F12 for Show Find Results Window
  • RIDER-7526 — VS Keymap: Ctrl+E,F for Silent Code Cleanup
  • RIDER-7527 — VS Keymap: Ctrl+E,C for Code Cleanup Dialog (non-slient)
  • Performance Problem:
  • RIDER-7239 — Freezes during typing F# code
  • RIDER-7374 — RavenDB save caches is very long
  • Task:
  • RIDER-6199 — Controller template should use dependencies accordingly to project type
  • Usability Problem:
  • RIDER-7294 — VS OSX keymap clash on Navigate Back and Collapse code
  • RIDER-7508 — Rider OSX keymap mixes Alt+ and CMD+ for toolwindows
  • RIDER-7516 — "Rider OSX" keymap missing unit testing quick list
  • RIDER-7660 — "Rider action: getting the action ready" tooltip appears very often when I paste F# code
  • RIDER-7718 — The Color Temperature of the Text on the UI is Too Cold (White)

New in Rider 1.0 Build 171.4456.902 EAP 24 (Jun 30, 2017)

  • Performance fixes.
  • F# Interactive tool window.
  • Unity plugin improvements.
  • Better validation and completion in web.config and app.config files.
  • File > Open merged with File > Recent Projects in application menu.

New in Rider 1.0 Build 171.4456.575 EAP 23 (Jun 17, 2017)

  • .NET Core debugger on Mac and Linux is back!
  • More debugger improvements: Console view is working again, Results view for enumerables, no more duplicating backing fields, etc.
  • Code Cleanup arrives in Rider.
  • F# unit testing and more F# support improvements.
  • Target frameworks can be shown in the Errors in Solution view when Solution-Wide Analysis is on.
  • Reworked Project Properties dialog and a new Solution Properties dialog.
  • VB.NET project templates.
  • Project load error notifications.
  • Improved support for web.config and MSBuild files.
  • Reworked console.

New in Rider 1.0 Build 171.4456.199 EAP 22 (May 19, 2017)

  • Support for Xamarin Mac and iOS applications.
  • Undo and redo are available for large-scale refactorings such as moving a class to a different project.
  • Unit testing improvements with new toolbars, context actions to manage test sessions from the editor, and more.
  • NuGet client receives UI to manage NuGet package sources.
  • Debugging two or more projects simultaneously via attaching to compound run configurations.
  • Build behavior and UI fixes.
  • Favorites tool window showing favorites, bookmarks and breakpoints.
  • More work on code inspection settings.

New in Rider 1.0 Build 171.4089.466 EAP 21 (Apr 28, 2017)

  • ntroducing F# support with a bundled plugin.
  • Microsoft's TFS plugin is back in Rider and is now bundled.
  • Syntax highlighting and navigation in XML documentation comments.
  • Rider's Settings dialog improved with NuGet options, ReSharper-based typing assistance options, etc.
  • An option to show members from related files in Go to File Member.
  • Detection of existing file indents in .NET languages.

New in Rider 1.0 Build 171.4089.265 EAP 20 (Apr 14, 2017)

  • Highlights:
  • Initial support for Xamarin Android applications.
  • Improved support for .csproj-based .NET Core projects.
  • Alt+Enter pop-up reworked: it allows searching for actions and settings (similar to ReSharper), and contains items provided by Rider's backend (ReSharper) and front-end (IntelliJ platform).
  • Custom tools to generate .Resx files, execute T4 templates (the latter is available on Windows only, requires Visual Studio SDK).
  • Node.js support based on WebStorm.
  • Stop All action is available in compound run configurations.
  • Code folding settings (imports are collapsed by default).
  • Word search in Rider's Options dialog and Search Everywhere pop-up.
  • NuGet improvements: performance tuning, advanced support for UWP projects and versions with asterisks (i.e. 1.0.0-*), an option to disable restore via NuGet.config.
  • More plugins are available for installation.
  • Bug:
  • RIDER-883 — Add Gulp support
  • RIDER-1181 — "Host not found" when opening a solution from the welcome screen
  • RIDER-1607 — Error trying to install package with more than one source Nuget origins
  • RIDER-2331 — Disambig need for add reference dialog
  • RIDER-2459 — Rename is case insensitive
  • RIDER-2722 — Rider insists on using @model instead of @Model
  • RIDER-2815 — Wrong templates completion in Razor files
  • RIDER-2823 — Rider Package Restore Does not Use Nuget Restore Settings
  • RIDER-3143 — Code Folding > Collapse by default > Imports has no effect
  • RIDER-3353 — Editing .resx files doesn't launch codebehind file generation
  • RIDER-3838 — nuget package from local disk not work
  • RIDER-3896 — no code highlighting on the left side of compare window when diff typescript file
  • RIDER-4175 — Alt + Enter menu is sometimes cropped
  • RIDER-4230 — Option to not restore .netcore packages when opening a solution
  • RIDER-4297 — "Delete ?" message when removing excluded file
  • RIDER-4369 — Rider EAP does not recognize LESS-files
  • RIDER-4373 — View for scratches
  • RIDER-4405 — Cannot select Alt+Enter menu item with Alt+Enter
  • RIDER-4439 — It takes too much time to find popular packages (API v2)
  • RIDER-4518 — Exception raised before LoggerHost has started isn't being logged
  • RIDER-4539 — New Scratch File has disappeared
  • RIDER-4702 — [Inspections] The identical icons in Inspection tool window
  • RIDER-4735 — Alt-Insert popup menu in solution explorer does not offer to create a new class when ordinary file is selected.
  • RIDER-4762 — Caption of the QF menu hides text
  • RIDER-4792 — Empty "Rename textual occurrences" window when renaming an element
  • RIDER-4802 — Odd button when commiting in git caused by TFS plugin
  • RIDER-4813 — New -> Directory doesn't work for Solution folders
  • RIDER-4818 — Sometimes feeds are doubled in the right drop-down list
  • RIDER-4918 — The type 'System.Net.Http.HttpMessageHandler' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
  • RIDER-4969 — exclude from project does not work
  • RIDER-5050 — There is no pre-installed File Watchers plugin
  • RIDER-5086 — Live template nguid is not accessible in completion but expands by tab
  • RIDER-5133 — Unit test session from 2nd instance is added to session from the 1st instance
  • RIDER-5170 — No bin/rider.sh in EAP Build 19 Tarball
  • RIDER-5192 — Provide warning message if Android SDK path not defined
  • RIDER-5220 — Search box blinks with red during typing
  • RIDER-5231 — PhpStorm-specific actions in Go to Action
  • RIDER-5233 — Open Xamarin project will not generate RunConfiguration
  • RIDER-5234 — Incremental build results view lacks scroll-bar
  • RIDER-5235 — Rider setting "Android SDK Path" doesn't affect $AndroidSdkDirectory which is used for Build or Deploy
  • RIDER-5269 — Nuget restore on startup breaks compilable solutions (Roslyn)
  • RIDER-5280 — Project load fails directly after dotnet.exe migrate
  • RIDER-5283 — Alt enter popup displays the popup on different monitor.
  • RIDER-5320 — restore nugets doesn't work in Rider, but works fine in VS14, VS15
  • RIDER-5333 — Every 3rd - 4th completion call hangs for 2 sec and throws an exception
  • RIDER-5341 — Rider shouldn't complete `#region` inside strings
  • RIDER-5471 — Android tests build process failed with errors
  • RIDER-5472 — AndroidApp build failed with following errors
  • RIDER-5485 — Buttons to Run/Stop application are disabled if Run on device failed for some reasons
  • RIDER-5618 — Settings on Mac: Unable to select an option in drop-downs
  • Exception:
  • RIDER-3345 — Exception in debugger process: Mono.Debugging.Evaluation.EvaluatorException: Unknown identifier: i at Mono.Debugging.Evaluation.NRefactoryExpressionEvaluatorVisitor.VisitIdentifierExpression(Identi...
  • RIDER-3722 — The text range must be normalized. Start: 9061, End: 9041
  • RIDER-4510 — Request to sync shared projectFile when there are normal project contexts
  • RIDER-4513 — IllegalArgumentException: Executing h2 with terminated lifetime
  • RIDER-4584 — TimeoutException: update failed for AnAction with ID=Debugger.AddToWatch
  • RIDER-5019 — The type initializer for 'System.Windows.UIElement' threw an exception. The method or operation is not implemented.
  • RIDER-5281 — Component JetBrains.ReSharper.Plugins.Unity.Psi.Resolve.UnityEventFunctionReferenceProviderFactory [Singleton, Corrupted] construction has failed. Component descriptor JetBrains.ReSharper.Plugins.U...
  • RIDER-5285 — Exception in debugger process: Unable to create debug session Could not locate CoreCLR Debug Files in the directory “C:Program FilesdotnetsharedMicrosoft.NETCore.App”. The Debugger Shim Library...
  • RIDER-5360 — IllegalStateException: Isolated exception: PopupInteractionModel.altEnterItemsContributor: Already terminated (Already terminated)
  • RIDER-5510 — ShellCommandUnresponsiveException: null
  • Feature:
  • RIDER-616 — Add Bower support
  • RIDER-695 — Package Installer for npm,bower and nuget(Feature)
  • RIDER-1030 — Provide an option to set custom path to Android SDK
  • RIDER-1126 — Make idea.max.intellisense.filesize accessible
  • RIDER-2039 — Support for processing T4 Template
  • RIDER-2506 — Javascript/Grunt support
  • RIDER-2833 — Alt enter with goto action
  • RIDER-3122 — Support for React JSX files
  • RIDER-3789 — better javascript support
  • RIDER-5189 — Show model of connected device and its API version in run dialog
  • Performance Problem:
  • RIDER-1935 — Slow 'shutdown' in tests
  • Task:
  • RIDER-5191 — Provide templates for Android applications
  • RIDER-5287 — Provide Error or Warning message if Android SDK path is not specified
  • RIDER-5430 — Plugin 'Docker integration' required plugin com.intellij.modules.remoteServers is not enabled.
  • Usability Problem:
  • RIDER-3967 — Display sub menus by hovering over it
  • RIDER-4691 — no collapsers for documentation before method

New in Rider 1.0 Build 19 EAP (Mar 23, 2017)

  • Initial support for .csproj-based .NET Core projects.
  • Additional tooling for front-end web development (courtesy of WebStorm), including support for:
  • LESS and Sass,
  • Bower,
  • npm, Gulp and Grunt runners,
  • JavaScript quality tools: JSLint, JSHint, Closure Linter, JSCS, ESLint.
  • Code inspection settings.
  • Find similar issues in file, project, solution or a custom scope.
  • Run inspection by name.
  • .NET-specific scopes in Find in Path.
  • Color picker window for C#, XAML and CSS.
  • Bug fixes and more contrasting colors in To-do Explorer.
  • No more high CPU usage caused by mono-sgen processes on macOS.

New in Rider 1.0 Build 18 EAP (Feb 24, 2017)

  • CoreCLR debugging on Windows is back (Linux, macOS to come later).
  • Debugger can attach to .NET Core processes on Windows.
  • Fixed solution load errors with Invalid volume separator char exception.
  • Support for COM references: UI for adding them, and properly displaying them in the Solution Explorer.
  • Fixed invalid dangling foldings in editors that haven't been opened for a long time.

New in Rider 1.0 Build 17 EAP (Feb 16, 2017)

  • Debugging .NET Core applications that target CoreCLR is temporarily disabled due to licensing issues. To learn more, see this blog post.
  • Debugger adds hit count filters for line breakpoints.
  • Support for shared projects.
  • NuGet: new NuGet Manager UI, improved support for project.json and Universal Windows Platform applications.
  • Fixes that address crashes, exceptions and slowdowns on solution load on macOS and Linux.
  • Code completion for colors in C#, XAML and CSS.
  • Summary info popup in code completion.
  • Unit testing: new settings page and a fixes related to unit test session management.
  • Low latency typing (most noticeable on Linux).
  • Improved code completion performance.
  • Build: improved navigation from build results, additional diagnostic actions.
  • Inspection severity configuration from the Alt+Enter menu.

New in Rider 1.0 Build 16 EAP (Jan 18, 2017)

  • The new build can open multiple solutions at once, supports EditorConfig, improves the debugger experience, and refreshes the NuGet tool window UI.

New in Rider 1.0 Build 15 EAP (Dec 20, 2016)

  • Code style settings for C#, VB.NET, JavaScript, TypeScript, CSS have been ported from ReSharper.
  • Improved automatic highlighting for usages of symbol under caret: no more blinking on moving the caret, and the error stripe starts to indicate highlighted usages.
  • Better syntax highlighting for ASPX markup.
  • More file templates: directories, generic files, HTML files, data sources.
  • C# code folding improved: more foldings for different language structures and blocks, including for, foreach, switch, using, if/else, try/catch/finally, lambda expressions, properties, and initializers).
  • Initial support for code folding in XAML, including folding for comments and tags.
  • Default project directory is now set correctly instead of pointing to the root directory.
  • Unity debugger learns to insert breakpoints in Unity 5.5.
  • Performance improvements and fixes in .NET Framework debugger (evaluating nullable properties, calling methods of generic classes etc.).
  • Version control improvements: better presentation of commit details, messages and labels in Git and Mercurial commit logs; new actions to undo the last commit and sign-off a commit.
  • Improvements in database editor, such as better usage search and editing multiple similar cells.

New in Rider 1.0 Build 14 EAP (Nov 28, 2016)

  • Initial support for new .csproj files introduced by Visual Studio 2017 RC.
  • Usages of symbol under caret are now automatically highlighted.
  • New unit testing actions, including Repeat previous run and Append tests to session.
  • A shortcut for Save document is introduced.
  • Multiple debugger and unit test runner fixes.
  • Python plugin is now available.