Roslyn

Code analysis is an important technique to keep our code clean, readable and free of defects. Besides its own code analysis features, Rider 2018.1 started to add support for Roslyn Analyzers, such as xunit.analyzers, which seamlessly blend into the familiar way of highlighting code inspections, configuring their severities or applying related quick-fixes. In Rider 2018.2, issues with .NET Core

Please welcome the new spring release of Rider! Our team has worked hard to make your experience with Rider even smoother and more enjoyable. Download JetBrains Rider 2018.1, or read on for release highlights. (more…)

In our previous post, we looked at how we can specify ReSharper's inspection severities inside our EditorConfig file. In this post, we will see how ReSharper and Rider integrate with Roslyn conventions. In this series: Maintaining consistent code style with formatting inspections Configuring inspection severities with EditorConfig Code style settings from Roslyn conventions in EditorCon

While writing code, Rider performs code analysis and helps us spot any errors, problems or potential improvements. With over 2.400 code inspections that come from ReSharper and WebStorm, Rider helps us improve code quality in every language it supports (C#, VB.NET, F#, HTML, JavaScript TypeScript, CSS, ...). The latest Rider 2018.1 EAP build goes one step further and adds Roslyn analyzer suppor

As you probably know based on news from BUILD Windows conference last week, Roslyn, the new .NET Compiler Platform with code analysis APIs for C# and VB.NET, has been pushed to Preview phase and open sourced. In case the event slipped your attention, here's a nice tour of Roslyn on the C# FAQ blog at MSDN. Immediately we at JetBrains were faced with multiple questions on the perspectives of ReS