In C# how many lines before a class should be consider to be refactored? [closed]

Answer 1

My rule of thumb is for methods, more than classes - If I can't see the whole method on screen it needs to be refactored. Of course, the traditional smells apply.

Answer 2

When the class violates the SRP, it's time to refactor.

The single responsibility principle is a computer programming principle that states that every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility

Answer 3

In C#, my rule of thumb for classes is anything over 500 lines is getting too long. I really like methods under 10 lines, and I guess under 20 is acceptable. I think it really depends on the context.

Answer 4

Refactor whenever you have the opportunity to:

• introduce the appropriate design patterns in lieu of spaghetti code
• reduce code complexity and increase readability
• remove redundant code by introducing a single method call
• extricate UI from business logic

etc, etc.

EDIT: Obviously, the decision to refactor should take into account time, potential pay-off, other responsibilities, etc.