Partial classes is excellent for readability, separating UI / logic, teams, etc. , but:
Is there any runtime benefits (i.e. memory use, loading UI (WinForms)) of saving / splitting different logical parts of a class into different files, or are me asking this question a tell-tale of poor design (my class need refactoring)?
Project scenario: Single developer, desktop-dev, winform displaying results of different types of filesearch (local computer). Some of the search-logic separated in a dll, rest is embedded in the winform-code. What started as a "You'll have it by the end of the week", became "Shure, I know UML" before I parted the threading logic, filtering, etc.
On Error Goto Hell