Posted on 07/06/2013 10:56:02
Hi Martin,
Developing on the server is indeed a bad idea; if your site is hosted in IIS, each developer works against the same physical folder on disk which is very problematic.
I would look into Microsoft's TFS solution. Although TFS can be quite a complex beast, installing it for just source control is relatively simple. In addition, you could choose to use the hosted solution at tfs.visualstudio.com (free for up to 5 developers).
WIth TFS installed, each developer can get the latest version of an application and the Dynamicweb Files folder (or just the Templates folder as I usually do) and work with that locally. Each developer can have its own local SQL Server database or they could share a single instance on the network. Each options has its own pros and cons. By sharing the database, you can get in each others way and maybe block developers from the work they are doing. By having your own copy you may have synchronization issues.
Dynamicweb doesn't have a good dev => test => acceptance => production story, so getting database updates from a dev machine into production will always be difficult. I usually propagate changes to /Files and the application (when doing custom development) from a release build on a dev machine to production and then manually redo changes to the database schema or content in Dynamicweb (pages, item type data and so on).
Hope this helps, and feel free to ask follow up questions.
Cheers.
Imar
