Requirements:

• Composite C1 1.2 SP2 (Patch 1) or later.
• Using the SqlDataProvider as storage.
• Version Control System which allows for editing files without explicit check outs (like SVN or CVS)

Setup:

1. Install C1 on machine A
2. Start C1 for the first time on machine A and then shut it down again by closing all browser windows and recycle the C1 IIS app pool.
3. Add and commit the Website folder to your favorite version control system (SVN/CVS/…). The following files and directories should not be added: /Bin/Composite.Generated.dll /App_Data/Composite/Cache /App_Data/Composite/ApplicationState
4. Checkout the website folder on machine B, C, … and setup IIS to use the newly checked out website folder.
5. Start using C1 on machines A, B, C, …

Day to day usage:

• Media files, template xml, xslt files etc. should be added when checking in. In short all files added to the website file structure (except those explicitly mentioned in step 3 above) should be added to your version control system.
• Commit and update often.

Possible conflicts

• When adding a new data type through C1 a commit has to be done on the machine that has added the new data type. This should be done as soon as possible, especially if the type is used in functions or page renderings.
• When changing a C# C1 data type the machines that haven’t updated their source might experience problems like, xslt rendering errors on pages. This can happen if a new property is added to the data type and this property is used in a rendering. The machines that haven’t updated their source will not have this new property until they update their source, but they are able to continue using C1 regardless. To away this, commit changes to data types as soon as possible.