Skip to content
  • Home
  • About
  • No Access
  • Privacy Policy
Bits of .NET
Bits of .NET
  • Asp.Net Core
  • C#
  • SQL
  • JavaScript
  • CSS
  • About
  • ErcanOPAK.com
  • No Access
  • Privacy Policy

Bits of .NET

Daily micro-tips for C#, SQL, performance, and scalable backend engineering.

  • Asp.Net Core
  • C#
  • SQL
  • JavaScript
  • CSS
  • About
  • ErcanOPAK.com
  • No Access
  • Privacy Policy
C#

C#: Why ‘throw ex;’ Instead of ‘throw;’ Erases the Real Stack Trace of Your Bug

- 31.08.26 - ErcanOPAK

🔧 One Word Difference Destroys Your Stack Trace

You catch an exception, log some context, and re-throw it with throw ex; so the caller still sees the error. Except now the stack trace points at your catch block instead of the line that actually failed — the real bug location is gone forever.

🐞 The Problem

try
{
    ProcessOrder(order);
}
catch (Exception ex)
{
    _logger.LogError(ex, "Order processing failed");
    throw ex;   // <- resets the stack trace right here
}

🔍 Why This Happens

"throw ex;" is treated by the runtime as a brand new throw
statement. The exception object is the same, but its StackTrace
property gets overwritten to start at THIS line, not the line
where the exception was originally raised inside ProcessOrder().
By the time it reaches your top-level error handler, every clue
about where things actually went wrong is gone.

✅ The Fix: Bare throw; Preserves Everything

  • Replace throw ex; with a bare throw; — same exception, same message, but the original stack trace stays intact all the way down to the failing line.
  • If you need to add context, wrap it instead: throw new InvalidOperationException("Order processing failed", ex); — the inner exception still carries its full original trace.

📦 Correct Version

try
{
    ProcessOrder(order);
}
catch (Exception ex)
{
    _logger.LogError(ex, "Order processing failed");
    throw;   // preserves the original stack trace
}

⚠️ Quick Rule of Thumb

  • Never type throw ex; in a catch block — if a code review sees it, it should be flagged every time.
  • Static analyzers (Roslyn CA2200) already catch this one automatically — enable it as a build warning-as-error if it isn’t already.

The exception object survives either way — only the trail of breadcrumbs leading back to the real bug depends on which keyword you type.

— C# Best Practice

Related posts:

The Hidden Cost of async Without await in Real Applications

The Hidden Cost of async Without await in Real Applications

Unicode — String Length Is Not What You Think

Unicode — String Length Is Not What You Think

C# Record Types: Immutable Data Patterns That Eliminate Bugs

C# Record Types: Immutable Data Patterns That Eliminate Bugs

Views: 8

Post navigation

SQL Server: Fix Deadlocks Between Two Queries That Update Tables in a Different Order
The AI Prompt That Turns a Long Group Chat Into a Clear Summary of Decisions and To-Dos

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

November 2026
M T W T F S S
 1
2345678
9101112131415
16171819202122
23242526272829
30  
« Oct    

Most Viewed Posts

  • How to make theater mode the default for Youtube (1,055)
  • Get the User Name and Domain Name from an Email Address in SQL (980)
  • How to add default value for Entity Framework migrations for DateTime and Bool (976)
  • Get the First and Last Word from a String or Sentence in SQL (857)
  • How to select distinct rows in a datatable in C# (852)
  • How to enable, disable and check if Service Broker is enabled on a database in SQL Server (653)
  • Add Constraint to SQL Table to ensure email contains @ (607)
  • Average of all values in a column that are not zero in SQL (569)
  • How to use Map Mode for Vertical Scroll Mode in Visual Studio (546)
  • Find numbers with more than two decimal places in SQL (475)

Recent Posts

  • C#: Fix a ConditionalWeakTable Entry Vanishing Too Soon
  • Docker: Fix a Stale COPY Layer After Editing .dockerignore
  • Photoshop: Fix a Pattern Overlay Scaling Wrong on a High-DPI File
  • SQL Server: Fix a Computed Column Index Skipped by Implicit Cast
  • HTML5: Fix a required Input Inside a Hidden Tab Blocking Submit
  • SQL Server: Fix ROW_NUMBER Ties Reordering Between Identical Runs
  • C#: Fix an Enum HasFlag Returning True for the Zero Value
  • WordPress: Fix Featured Images Vanishing After a CDN Migration
  • Photoshop: Fix Content-Aware Fill Smearing a Repeating Pattern
  • Asp.Net Core: Fix Antiforgery Tokens Rejected Behind a Reverse Proxy

Most Viewed Posts

  • How to make theater mode the default for Youtube (1,055)
  • Get the User Name and Domain Name from an Email Address in SQL (980)
  • How to add default value for Entity Framework migrations for DateTime and Bool (976)
  • Get the First and Last Word from a String or Sentence in SQL (857)
  • How to select distinct rows in a datatable in C# (852)

Recent Posts

  • C#: Fix a ConditionalWeakTable Entry Vanishing Too Soon
  • Docker: Fix a Stale COPY Layer After Editing .dockerignore
  • Photoshop: Fix a Pattern Overlay Scaling Wrong on a High-DPI File
  • SQL Server: Fix a Computed Column Index Skipped by Implicit Cast
  • HTML5: Fix a required Input Inside a Hidden Tab Blocking Submit

Social

  • ErcanOPAK.com
  • GoodReads
  • LetterBoxD
  • Linkedin
  • The Blog
  • Twitter
© 2026 Bits of .NET | Built with Xblog Plus free WordPress theme by wpthemespace.com