Using Source Control
In a typical networking environment, each developer has his or her own local source files on their workstation machine. When a developer wants to make a change to a file, they first “check it out” using source control software. After the file is checked out, they edit a local version of the file with Source Insight. When the developer is satisfied that they want to keep the changes made, they check it back in using their source control software. This effectively copies the file from the developer’s local machine back to the main project server.
When another developer wants to get the “latest and greatest” version of the source files, they use the source control software to “synchronize” their local directories with the main project server. This effectively copies newer files from the project server to the developer’s local workstation machine.
Source Insight recognizes when files change by checking each file’s “last-write” timestamp, and the file’s size. When it detects that a file has changed, it re-parses the file and updates the Source Insight symbol database on the developer’s local machine.
In this section: