The JetBrains Blog

Blog

  • Blogs by Topic
    • English
    • Deutsch
    • Español
    • Français
    • 日本語
    • 한국어
    • Русский
    • 简体中文
    • Português do Brasil
    • Türkçe
    • IDEs

      • AppCode
      • CLion
      • DataGrip
      • DataSpell
      • Fleet
      • GoLand
      • IntelliJ IDEA
      • PhpStorm
      • PyCharm
      • Rider
      • RubyMine
      • WebStorm
    • Plugins & Services

      • Big Data Tools
      • Code With Me
      • Quality Assurance
      • JetBrains Platform
      • Rust
      • Scala
      • Toolbox App
      • Writerside
    • Team Tools

      • Datalore
      • Space
      • TeamCity
      • Upsource
      • YouTrack
      • Hub
      • Qodana
    • .NET & Visual Studio

      • .NET Tools
      • ReSharper C++
    • Languages & Frameworks

      • Kotlin
      • Ktor
      • MPS
    • Education & Research

      • Edu Products
      • Research
    • Company

      • Company Blog
      • Security
Dotnet logo

The .NET Tools Blog

Essential productivity kit for .NET developers

Follow
  • Follow .NET Tools:
  • share
  • RSS
Get Tools
Follow
  • Follow .NET Tools:
  • share
  • RSS
  • All
  • How-To's
  • Releases
  • Webinars
  • Events
  • .NET Annotated
  • Rider
  • ReSharper
Get Tools

Exception

Exploring exception stack traces with ReSharper and Rider

We have all experienced bugs that throw exceptions in our applications. Using ASP.NET and getting a “yellow screen of death” (YSOD) with an exception message and stack trace? Using .NET Core and seeing stack traces printed to log files? With ReSharper and Rider, we can explore and navigate stack traces from these exceptions better within the IDE. Let's take a look at using the Stack Trace Explorer! (more…)

Chris Woodruff Chris Woodruff

Exception popup, improved Smart Step Into, symbol servers, and more Rider 2018.1 EAP debugger updates

The first build of the Rider 2018.1 EAP comes with a series of improvements for the debugger. We've added a new exception popup, improved Smart Step Into, third-party code can now be debugged using external symbol servers and SourceLink (or via decompilation), we now display source code for return value locals, the process username is displayed in the attach window, and several fixes were made to existing debugger functionality. More than enough to dig a bit deeper! Exception popup Up to this point, Rider already provided several ways to look into an exception, helping us figure out why a gi

Maarten Balliauw Maarten Balliauw
  • Privacy & Security
  • Terms of Use
  • Legal
  • Genuine tools
  • English
  • Deutsch
  • Español
  • Français
  • 日本語
  • 한국어
  • Русский
  • 简体中文
  • Português do Brasil
  • Türkçe
Copyright © 2000–2022 JetBrains s.r.o.