The best way to learn / research / understand the class hierarchy and how a new project works

Imagine this situation. You get some old code or get a new framework. You need to learn and understand how to work with this code as soon as possible. Unable to get help from a previous developer. What are the best methods / methods / methods / steps / tools (preferred .NET Framework tool stacks) to take maximum advantage when exploring a new code base.

If this is a structure and there is no documentation or unit tests, what tools do you usually use to study the hierarchy of classes, methods, events? Is it the default "Object Browser", "Architectural Explorer" of MS Visual Studio or some other tools, such as hierarchy / file representation of Resharper?

+5
source share
6 answers

Actually, this is not the best way to do this, since there are so many variables, and each project is different from the next.

To be completely honest, the best way to draw attention to it is to create an environment for the sandbox / test and, if you want a better description, play with it. Then play with him some more.

" ", , . , , . .

+3

- , , - , Enterprise Architect . , , VS.

, , Resharper, VS2008 ( ...) VS2010 ( ...).

, , , , ...

+1

, - .

, , , .

, / . .

0

, - , , ! , , , . , , ...

0

VS2010 Architecture, .

0
  • . .
  • Dll, . , .
  • .
  • Then you can run the application and check out some of the logs that will give you an idea of ​​the flow of classes and functions.
  • Then you can start by debugging the code / module that is assigned to you from above.

Now you can improve your settings.

0
source

All Articles