为什么MS CRM中托管和非托管解决方案文件有如此大的不同？ [英] Why Managed and Unmanaged solution files are so much different in MS CRM?

问题描述

我在MS Dynamics CRM中创建了解决方案，然后将其导出为托管和非托管解决方案。都解压缩，然后在 customizations.xml 文件上运行了diff工具。而且它们之间有太多差异，很难说到底是什么更改以及为什么更改。

I created solution in MS Dynamics CRM, then exported it as managed and unmanaged one. Decompressed both and I ran diff tool on customizations.xml files. And there are too many difference between them, it's hard to say what exactly what was changed and why.

这些更改是否至关重要？

Are these changes are crucial?

我可以仅通过将< Managed> 标记中的值更改为来创建托管解决方案1 而不是 0 ？会安全吗？

May I create managed solution just by changing value in <Managed> tag to 1 instead of 0? Will it be safe?

推荐答案

如果要将解决方案交付给客户，打包带有适当发布者和版本的适当托管解决方案，将是非常关键的部分。

If you are shipping your solution to customer packaging a proper Managed Solution "with proper publisher and version" will be very critical part.

如果您要深入了解自定义，您将了解到，仅更改托管标签并不能真正解决问题。

If you'll go deep into customization you'll understand that only changing managed tag doesn't really make a solution Managed in Proper Sense.

通过更新托管标签，您可以从CRM中安装/卸载解决方案，但是如果您深入了解托管解决方案的正确用法，则可以在字段级别控制哪个字段将可自定义，而哪个字段将不可自定义，这样您就可以控制CRM，使以后导入的其他解决方案不会破坏您的自定义，您将开始看到差异。

By Updating Managed tag you can install/uninstall solution from the CRM but if you'll get deep into proper usage of Managed Solution where you control at field level "which field will be customizable and which field won't be customizable" so that you can control CRM in such a way that other solutions which are being imported afterwards don't break your customizations, you'll start seeing the differences.

这篇关于为什么MS CRM中托管和非托管解决方案文件有如此大的不同？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！