I can't speak for the gp, but they were talking about inheriting a project/legacy code.
If I end up needing to go through legacy code, and there are a lot of gnarly, long methods/blocks, I'll usually add comments and regions to it as I go along. I'll use comments if I just want to note something, and a region if I want to note something about a region of code. It's my rough map. Being able to tell Visual Studio to arbitrarily collapse an area is handy for sketching it. The long term goal is to refactor, but it's handy as a way to quickly outline things.
Re:Windows CoreAudio API in C#
by kenjackson on Thursday February 04, 2016 @11:53PM
(#11039538)
Point me to some of your code and I bet it would benefit from well placed regions.
Plus you're now burying how long your class is and the individual methods within. So a class or method that would otherwise be inappropriately long now looks a reasonable length.
If you feel like the code is so long that it needs regions, then refactor the code, don't hide the mess under the bed.