The information in this article applies to:
SUMMARYThe general rule of thumb for adding files from a Visual C++ project to source-code control is: If the file is text, it is probably OK to add; if the file is binary, it probably should not be added. MORE INFORMATION
When checking in files, Visual C++ will automatically prompt you to check
in all files in the Project Workspace Pane plus the project makefile
(.mak). In most cases, these will simply be the source files needed to open
and rebuild your Visual C++ project.
Usually, these files cannot be easily regenerated. There are issues that
need to be considered when sharing a makefile through source-code control.
These issues are discussed in the Visual C++ Online documentation. Please
see the REFERENCES section below.Following is a (non-exhaustive) list of file extensions for files that should not be added to source-code control under normal circumstances :
Usually, these files are automatically regenerated by Visual C++ in
opening, editing, and building the project.
REFERENCESFor additional information, please see the following article in the Microsoft Knowledge Base: Q132340 Common File Extensions Used by Visual C++"Maintaining Makefiles Under Source-Code Control" and "Putting Files Under Source-Code Control" from the Visual C++ Online documentation. Additional query words:
Keywords : kbinterop kbSSafe400 kbSSafe500 kbSSafe600 kbVC400 kbVC500 kbVC600 |
Last Reviewed: November 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |