Best Practices for Concurrent Development of CRM 2011

Question

What are the best parallel development solutions for CRM 2011? What is the proper way to handle changes in settings for different developers?

Assuming each developer has their own local dev environment and there is a dev community environment ...

How do developers avoid overwriting each other when they “check” / import their settings with the community development server? How do developers avoid overwriting their local work when they “check” / export settings from the community server and then try to import them?

What tools are commonly used to automate this process?

Answer 1

Here are some best practices ...

First, it’s just a web resource naming convention. At Customer Effective, we chose cei _ / {project} / {type} / {filename}. {Extension}. An example would be something like cei_ / BingMaps / html / multiLookup.htm. Thus, it is easy to find, and we are consistent.

Now we usually do not develop a team, but if you do, you will definitely want to use SVN. We use SVN, but mainly for backing up an individual user and links to other elements.

Another best practice is to create a Dev / UAT / Prod environment. I also highly recommend having a Vanilla environment for those who make the decision for more than one client.

, . . , .