并发 CRM 2011 开发的最佳实践
在 CRM 2011 中处理并发开发的最佳实践是什么？处理不同开发人员对定制的更改的正确方法是什么？
假设每个开发人员都有自己的本地开发环境，并且有一个社区开发环境...
开发人员在使用社区开发服务器“签入”/导入自定义内容时如何避免覆盖彼此的工作？当开发人员从社区服务器“签出”/导出自定义内容然后尝试导入它们时，如何避免覆盖其本地工作？
通常使用哪些工具来帮助自动化此过程？
What are the best practices for dealing with concurrent development in CRM 2011? What is the proper way to deal with changes to customizations by different developers?
Assuming that each developer has their own local dev environment and there is a community dev environment...
How do developers avoid overwriting each other's work when they "check in" / import their customizations with the community development server? How do developers avoid overwriting their local work when they "check out" / export customizations from the community server and then attempt to import them?
What tools are typically used to help automate this process?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这里有一些最佳实践...
首先，只是网络资源的命名约定。在 Customer effective 中，我们选择了 cei_/{project}/{type}/{filename}.{extension}。例如，cei_/BingMaps/html/multiLookup.htm。这样很容易找到，而且我们是一致的。
现在我们通常不进行团队开发，但如果您这样做，那么您肯定会想要使用 SVN。我们使用 SVN，但它主要用于个人备份和引用其他成员的内容。
另一个最佳实践是拥有 Dev/UAT/Prod 环境。我还强烈建议为那些为多个客户提供解决方案的人建立一个普通环境。
最后，切勿在非托管解决方案中包含站点地图或功能区。相反，有一个站点地图解决方案和一个功能区解决方案。否则，如果最新的非托管解决方案共享实体功能区，则它们将覆盖以前的解决方案。
Here are a few best practices...
First, is simply the naming convention of web resources. At Customer Effective, we opted for cei_/{project}/{type}/{filename}.{extension}. An example would be something like cei_/BingMaps/html/multiLookup.htm. This way it is easy to find and we are consistent.
Now we don't typically team develop, but if you do then you will certainly want to use an SVN. We use an SVN but it's mainly for backups of the individual and referencing other members stuff.
Another best practice is to have a Dev/UAT/Prod environment. I would also strongly suggest having a Vanilla environment for those who would make a solution for more than one customer.
Lastly, never include a sitemap or ribbon inside of your unmanaged solutions. Instead have a single sitemap solution and a ribbon solution. Otherwise, the most recent unmanaged solution will overwrite the previous if they both share the entity ribbon.