Skip navigation
Currently Being Moderated

What Should *and* Should Not Go Into Source Control?

Aug 10, 2011 10:17 AM

I've seen posts with tidbits of what should not go into source control, but I haven't seen a comprehensive list of what should and should not go into source control. Does anyone know? Here's what I know so far - do not put the following files in source control: .pss, .cpd, .ldb and .hhp.


Right now I'm wondering about the XPJ file. If two or more people are working on a project, should this file be source controlled?


Is there a specific list of files that DO need to be in source control in order to maintain the project's integrity?

  • RoboColum(n)
    5,356 posts
    Oct 8, 2004
    Currently Being Moderated
    Aug 11, 2011 3:30 AM   in reply to LaKisha1

    The simple answer here is that machine specific files do not need to be checked in. This includes .PSS and .CPD files. The .HHP and .XPJ files are not machine specific, they are project specific and therefore must be checked in. The confusion over the HHP file may come down to whether CHM output is being produced. If you are not, you could safely say that this file need not be source controlled. However it doesn't cost anything to include it under source control so why make life more difficult by excluding it.


      The RoboColum(n)   @robocolumn   Colum McAndrew
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points