I needed to understand a large legacy .NET codebase — so I built a tool for it

I’m a .NET dev, and lately I’ve been slowly open-sourcing some of the small things I built for myself over time. This is one of them. The context I’ve been working on an old .NET 4.6 app recently (~15 years old, 1M+ LOC). At some point I needed a way to understand the architecture better. Not in a “read the code” sense, but like: what depends on what where things are going in the wrong direction if there are cycles hiding somewhere You can navigate the code, sure. But getting a real picture of h