What is the best way to get acquainted with the estimated size 200K LOC's C # codebase? Is any device available?
It seems that there is a long time for this purpose.
Thank you.
A codeab is a great view; It uses the metaphor of a city that produces a lot of emotions, as well as highlighting the code.
Very good for an observation.
There is a good view for duplication, it parses your code-base and sees it through a wheel, where repetition is represented by a spokesperson in the wheel and you are given a party-per- The sides can hover on each to see diff.
There is a good LinqToCode type to implement quality barriers you can run these rules from the command line as part of a build-up.
Navigation features are unique to find out what uses- Find-Usage is very useful. For the search of a codebase, Alt + F7 is your friend, because it's run by you The history of the questions will also open, so that you can jump back and forth to keep your place.
Visual Studio keeps a record of cursor positions / editor points and ctrl + - and ctrl + shift + to move the cursor back and forth between them.
You can insert notes yourself if you decide on a comment that is conventional (for example, // note: Bla) and then to find all these remarks, Use the Todo Explorer (and other patterns you can define), then navigate through them. For example, we currently use it for code-review.
Visual Studio (at least, business edition) can generate a class diagram; Multi-select files, and right-click then create a class diagram. I get this more useful as a disturbance, as opposed to an artwork and in sync with Codebase, however, clearly it will tell you the heritage but will not show the tools - very clearly the interface, and Will not even attempt to collect or create.
Comments
Post a Comment