Dynamics 2011-基本库解决方案中应包括什么？ [英] Dynamics 2011 - What should I include in my base Library Solution?
问题描述
我正在尝试整理一种最佳实践方法来组织解决方案，更具体地说，应该在基本解决方案或库解决方案中包含哪些内容。
SDK表示以下内容：
解决方案库对于具有多个解决方案或大型
企业部署的ISV，预计
必须共享许多解决方案组件。
解决方案共享组件的最佳方法是
创建解决方案库。通过在单独的
组织中创建
非托管解决方案，然后将这些
组件打包到托管解决方案中，可以创建
解决方案库。
将托管解决方案安装到另一个组织
中，让
开发人员从他们
创建的解决方案中引用这些共享的
组件。
Microsoft Dynamics CRM解决方案
框架使您可以构建相互依赖的
解决方案层。
通常，您创建一个表示基本
解决方案的解决方案
库。可以在此基础解决方案之上构建其他解决方案
。
理想情况下应在基础/库中放置哪些组件解？核心业务实体和选项集？
动力学文档似乎没有很多指导。
如果您计划在多个组织之间共享任何功能，这些功能将与组织的其余部分分开进行修订，那么我会考虑将其放在单独的解决方案中。
另一种可能性是在多个组织中使用的一组常见的JavaScript库和插件，例如用于自动命名或自动编号记录或某些自定义业务逻辑验证的事情。这样，如果您发现它们中的任何错误，就可以再次将相同的更改推送给所有组织。
如果您没有多个CRM组织，或者您没有独立软件开发商（ISV），我不会理会解决方案。它们对于CRM而言是一个巨大的飞跃，但这绝对是第一步，与它们一起工作会有些怪癖和头痛。
I am trying to sort out a best practise approach to organising solutions and more specifically what should be included in the 'base solution' or 'library solution'.
The SDK says the following:
Solution Libraries For an ISV with multiple solutions or a large enterprise deployment, it is expected that many solution components will have to be shared. The best ways for solutions to share components is to create solution libraries. You create a solution library by creating an unmanaged solution in a separate organization and then package those components into a managed solution. Install the managed solution into another organization and let developers reference these shared components from the solutions they create.
The Microsoft Dynamics CRM Solutions Framework lets you build layers of solutions that depend on each other. Typically, you create a solution library representing a "base" solution. Other solutions can be built on top of this base solution.
What components should ideally be placed in the base/library solution? Core business entities and option sets? Core functionality and workflows?
There doesn't seem to be a great deal of guidance on the dynamics documentation.
If you have any functionality that you plan to share across multiple organizations that will be revisioned separately from the rest of your organization, then I would consider putting that in a separate solution.
For example, say you have multiple regions in your business that will each have their own CRM organization, but each of them uses a standard way of scoring and assigning leads. In this scenario, I'd create a solution that encompasses that functionality and install it on each organization, and that way when the process changed, the same solution could be pushed out to all the orgs and everyone would get the same changes.
Another possibility would be a common set of JavaScript libraries and plugins that you'd use across multiple organizations, maybe for things like autonaming or autonumbering records, or some custom business logic validation. That way if you found any bugs in them, you again could push the same changes to all orgs.
If you don't have multiple CRM organizations or you're not an ISV, I wouldn't bother with solutions. They're a great leap forward for CRM, but it's definitely the first pass around, and there are some quirks and headaches to working with them.
这篇关于Dynamics 2011-基本库解决方案中应包括什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
