Home/ Questions/Q 613167
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T17:58:23+00:00

We’re working simultaneously on SharePoint sites. We’ve to move them on a source control

  • 0

We’re working simultaneously on SharePoint sites. We’ve to move them on a source control system. We’ve got both VSS and TFS. We’ll prefer TFS over VSS because of its reliability. I don’t have any idea how to bind a SharePoint site with TFS? The reason it is a bit confused with SharePoint site is not all dependencies are in there in the site it could have Layouts, Features etc. and they are deploy outside the site folder. How could you manage the separate pieces of a SharePoint site through a version controller (or TFS)?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is one of the problems with SharePoint development.
    We don’t keep any ‘content’ in source control, all that goes in there is the code, including everything we add to _layouts.
    Content (everything that is in a content database) still is an integral part of ‘the solution’. We use the versioning that is built into SharePoint for that and the integration server contains the source copy for all to get copies from. Content doesn’t deploy the same way as code so it is not included in builds.

    In some projects this may be possible using exports and imports or backups; every developer checks in an export of the site that the solution uses and this can be restored on the other development environments. This won’t allow merging and overwrites the developers own content.

    • 0