You said it. You can tell from the code that the developers had no concept of modular development. And that goes back to the ***1970s***, what was then called structured programming. They would just keep slinging heaps of procedural code at the problem until it kinda worked. Or didn't ;-)

>9000 lines of code ?
>That's an application not a method :-}
>Seriously, I cannot even conceive of a method requiring that amount of logic. Small wonder the maintenance requirement is so high...
>
>>I am working with a legacy system these days. The other day I came across a method with over 9000 lines of code ;-)
>>
>>>Yes, C sharp has partial class files but I do not use them for general classes. I do not like looking in partial classes to find the code, I like it organized in a single code file for a class. However, I also keep my code limited in a class to what the class should be responsible for and refactor out any base code, etc. I do not have classes that contain thousands of lines of code. I use regions only to collapse specific areas like Viv mentioned that allows me to scroll much easier when needed or to just view some methods or ??.
>>>
>>>Thanks
>>>
>>>>Tim,
>>>>
>>>>I sometimes use several files to split
>>>>
>>>>>In my opinion the #region is goog organization of code and I use much the same as Viv. Using ReSharper helps navigate code but sometimes for instance if I have many properties in a class, collapsing the region around the properties makes the file more manageable to wonder through. I don't view it as hiding code, but rather just part of organizing.
>>>>>Just another view point.
>>>>>Timothy
>>>>>