看完this SO question ,我注意到 link in the question引用了Microsoft.Xrm.Client.CodeGeneration.CodeCustomization,Microsoft.Xrm.Client.CodeGeneration
.
与标准代码生成相比,它有什么优势?根据 LameCoder,它将所有实体更改为从 Microsoft.Xrm.Client.CrmEntity
继承。而不是`Microsoft.Xrm.Sdk.Entity。这会产生哪些变化以及产生了哪些其他变化?
最佳答案
这里是 best site I could currently find关于它的作用:
- CrmSvcUtil & OrganizationServiceContext enhancements such as lazy loading
- Simplified Connection Management with Connection Dialog UI
- Client Side caching extensions
- Utility Extension functions for common tasks to speed up client development
- Organization Service Message utility functions to make it easy to call common messages such as BulkDelete, Add Member to Team etc.
- Objects to support the Microsoft.Xrm.Portal extensions
我可以看到从 CrmEntity 继承的唯一真正的缺点是它需要 Microsoft.Xrm.Client dll 在服务器上被 Gac'd 或 IL 合并到 Entities dll 中。
除了这个缺点之外,我看到它添加了以下功能:
System.Data.Services.Common.DataServiceKeyAttribute
System.Data.Services.IgnorePropertiesAttribute
(我假设这个通过网络发送的数据较少?)关于dynamics-crm-2011 - 引用 CodeGeneration.CodeCustomization 对早期绑定(bind)生成的 CRM 实体有何变化?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/21270081/