I think the best way is to make use of some kind of source control system like bitbucket or github so each developer has a local and central repository with the code. This way it's easy to work with multiple colleagues on the same project and merging files is usually pretty intelligent so it should not create too many issues when merging code.
It also has the benefit that you can make branches so you can work on your own branch on a specific project and merge it with the main branch once this specific feature is done for instance.
Are there any more specific details you want to know about?
We have a staging install that we do all editing and development on. We then use Courier to deploy the changes.
We have designers and editors on the same system. I have added a few customizations to the staging server including the following.
The ability to Lock items(pages, scripts, templates, macros, etc) and prevent them from being deployed accidentaly.
A Recent Changes dashboard that shows all recent undeployed changes to users can make sure they arn't updating something already being worked on.
Extra details on the General properties tab of pages including the last deployment date and number of unpublished revisions.d
A Compare with Production feature to check the differences between two items before deploying them.
In addition to this the editors use other communication tools to ensure they are not ocnflicting with eachother.
For backend development we have a seperate development instance that we include in out VS projects and build packages to customize and extend the system. The above customizations for example are all created as seperate project/packages in visual studio and then installed onto the staging and production servers. In this case we use source control software to handle changes, logging, and history.
Best way to work as a team in umbraco in Visual Studio 2010?
What is the best way to work as a team in umbraco in Visual Studio 2010?
Hi Denism8
I think the best way is to make use of some kind of source control system like bitbucket or github so each developer has a local and central repository with the code. This way it's easy to work with multiple colleagues on the same project and merging files is usually pretty intelligent so it should not create too many issues when merging code.
It also has the benefit that you can make branches so you can work on your own branch on a specific project and merge it with the main branch once this specific feature is done for instance.
Are there any more specific details you want to know about?
/Jan
We use the following setup:
We have a staging install that we do all editing and development on. We then use Courier to deploy the changes.
We have designers and editors on the same system. I have added a few customizations to the staging server including the following.
is working on a reply...