Sometimes doing arbitrary stuff feels just good! So let's do that!

We Are .NET

A playful exploration of .NET internals through the lens of creating the longest possible exception message in C#. The post walks through why `new string('X', int.MaxValue)` throws an OverflowException (a single object can't exceed 2 GB, and chars are 2 bytes each), how to find the practical upper limit by accounting for object metadata overhead, and why throwing that string as a standard Exception fails because `Exception.ToString()` tries to allocate an even larger string. The solution is a custom exception class that overrides both `Message` and `ToString()` to avoid the extra allocations.

Being stupid is fun: Let's create long exception messages!

<p>I enjoyed this, a fun concept to investigate</p>
