Dotnet logo

.NET Tools

Essential productivity kit for .NET and game developers

How-To's

Catching up with JetBrains Rider – Talk Recordings

On March 28th we held a special evening of Rider talks at JetBrains Munich office. We would like to thank everybody who was able to join us and make the event a great success.

For those who couldn’t join us in person, we are happy to share the following recorded talks in the playlist below: A Lap Around the Latest Rider 2017.3, .NET Performance Issues and Optimizations in Visual Studio / Roslyn / ReSharper / Rider, and Debugging Tips & Tricks in Rider. Full talk descriptions can be found below.

A Lap Around the Latest Rider 2017.3 — Matthias Koch
For a minor release, Rider 2017.3 introduced tonnes of new functionality. In this talk we tour what’s new: project templates and how to create them (hint: dotnet new), debugger improvements such as smart-step into, and debugging of third-party code without any effort. And since Rider is based on both ReSharper and IntelliJ IDEA, we look at the features these bring to the table: a reworked code formatting engine, extracting code into local functions, C# 7.1 and C# 7.2 support, a new editor-based REST client, and much more.

.NET Performance Issues and Optimizations in Visual Studio / Roslyn / ReSharper / Rider — Kirill Skrygan
Interested in writing high-performance .NET applications? In this talk, we tour some common .NET Performance practices (GC, Memory footprint, UI smoothness, …), with real-world examples which affect the IDEs you use every day. We peek under the hood of Visual Studio, ReSharper, and Roslyn, and discover the basic architecture of these gigantic .NET products. You will finally understand why Visual Studio is slow on big solutions (and always will be); what is beautiful about Roslyn, why ReSharper can slow down Visual Studio even more, and why Rider is technically the next generation of all IDEs.

Debugging Tips & Tricks in Rider — Matthias Koch
When I started in software development, I was writing “echo” statements in the code to see what was happening. We’re beyond that era, but do we know how to use all of the debugging tools that are available to us? In this talk, we see how we can greatly improve our debug-fu, and take a look at the debugger tools available in Rider. This is a practical demo-driven session, with tips and tricks on how to use the tools that help us troubleshoot and find bugs much easier!

image description