Geek Answers Handbook

How to reorganize closely related classes?

I am trying to reorganize a large closely related application and trying to make it more convenient and flexible.

I have a lot of unit tests, so I hope to reorganize step by step.

What design and refactoring patterns should be considered when implementing / applying to accomplish this task?

I may think of some:

Also feel free to share your experiences and best practices for such refactoring work.

UPDATE

I am doing this refactoring due to the reasons explained in this question . Basically, I cannot implement a plug-in system without extracting a couple of interfaces, and these interfaces are tightly coupled, which requires a separate application in 40 + DLLs to just compile without a circular reference.

+3
source share
6 answers

Thanks for all the answers. After struggling with a lot of different ways, I found it best to create interfaces for everything. This allowed me to freely change the design, and I just broke the assembly into a day (a day, because the project was large, and I need to fix so many links and unit tests + some refactoring).

.

, , , .

0

, . , , , , , , .

, , (, , , , ..). , , , , - .

, , , , . .

, , / . , .

+8

, . , - . . , .

. Code Complete, Pragmatic Programmer , .

+8

. .

+5

, . , . (, ..), . , , factory .

+1

Phlip:

It is very difficult for me to say which specific refactorings are suitable in your particular case without additional information.

0
source

More articles:


All Articles