Can’t Debug After Running Benchmark.net
Quick post to explain why you might not be able to debug your C# Visual Studio code or debug your unit tests after running Benchmark.net.
How quick is a quick post? Well:
🤔Did you forget to switch back to the debug config? 🤔
I've spent a non-zero amount of time wondering why I can't debug my code or unit tests after running benchmark.net and it's because I put the code into release configuration such that the benchmarking is more accurate.
You know, this:
This post is kinda gonna be like equivalent of:
"Do senior devs still have to look up stuff on StackOverflow?"
— Ryan Cavanaugh (@SeaRyanC) April 8, 2022
Gentle reader, I have gone to StackOverflow to read answers that I wrote about behavior that I myself designed and implemented.
Or this...
I'm a principal software engineer who's trusted to go around and find, fix, and improve the things that need it without little supervision.
— Nick Craver (@Nick_Craver) April 6, 2022
And yet, I just spent 20 minutes debugging missing file output because I had the folder sorted by type and not name. Dammit.
It happens. Good luck to you, dear reader 👍