Configuration/source control for a Visual Studio project
-
Hi all! Setting up a multi-developer Visual C++ project, which non-code files (i.e. not h- or cpp-files) would You include for source control? Obviously, all h- and cpp-files dhould be included, but then what? There has been some debate going on at the office on whether for instance the dsp and dsw files should be configured. A concrete example: we have suffered problems with what files/classes show up in a clients view after a sync to head following the check-in of new files/classes by another developer. By the way, we are using Perforce. Your input will be much appreciated! ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"
-
Hi all! Setting up a multi-developer Visual C++ project, which non-code files (i.e. not h- or cpp-files) would You include for source control? Obviously, all h- and cpp-files dhould be included, but then what? There has been some debate going on at the office on whether for instance the dsp and dsw files should be configured. A concrete example: we have suffered problems with what files/classes show up in a clients view after a sync to head following the check-in of new files/classes by another developer. By the way, we are using Perforce. Your input will be much appreciated! ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"
Less than a minute after posting my question I googled out the following page: http://www.perforce.com/perforce/doc.031/manuals/p4plugins/02\_visualcpp.html Scroll down to the second last heading; "which files do I put in the depot?". Any additional thoughts and input on the subject from You guys out there are still much appreciated! ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"
-
Hi all! Setting up a multi-developer Visual C++ project, which non-code files (i.e. not h- or cpp-files) would You include for source control? Obviously, all h- and cpp-files dhould be included, but then what? There has been some debate going on at the office on whether for instance the dsp and dsw files should be configured. A concrete example: we have suffered problems with what files/classes show up in a clients view after a sync to head following the check-in of new files/classes by another developer. By the way, we are using Perforce. Your input will be much appreciated! ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"
DSP's yes, DSW's no. If you are relying on your DSW to build the project correctly (via project dependencies), that's not a good thing. DSW's are intended for per-developer settings, DSP's for project settings.
Lets be honest, isn't it amazing how many truly stupid people you meet during the course of the day. Carry around a pad and pencil, you'll have twenty or thirty names by the end of the day - George Carlin Awasu 2.1.1 [^]: A free RSS reader with support for Code Project.