{"id":4567,"date":"2017-02-23T18:27:03","date_gmt":"2017-02-23T12:57:03","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=4567"},"modified":"2017-02-23T18:27:03","modified_gmt":"2017-02-23T12:57:03","slug":"watch-out-for-issues-with-version-updating-plugin-in-assembly-in-dynamics-365crm","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2017\/02\/watch-out-for-issues-with-version-updating-plugin-in-assembly-in-dynamics-365crm\/","title":{"rendered":"Watch out for Issues with Version & Updating Plug-in assembly in Dynamics 365\/CRM"},"content":{"rendered":"

Introduction:<\/strong><\/p>\n

Plugin Assemblies are versioned and need to be signed with a strong key for them to be registered to Dynamics CRM.<\/p>\n

Any update to the library and compiling the project may cause the version # to change or to maintain versioning practices you may decide to change the version # and this can cause problems when updating the plugin through Plugin Registration Tool for Dynamics CRM\/365<\/p>\n

Issue:<\/strong><\/p>\n

\u201cPlug-in assembly does not contain the required types or assembly content cannot be updated.<\/em><\/strong>\u201d<\/p>\n

You might receive the above error when updating an existing plugin assembly with the same code base as before.<\/p>\n

When we register a plugin, the project has an assembly information as seen below;<\/p>\n

\"Plugin-in<\/p>\n

This Assembly Information comprises of <Major Version><Minor Version><Build Number><Revision>.<\/p>\n

After code change we decided to change the Assembly version from 1.0.0.1 to 2.0.0.0 and while dong so using the Plugin Registration Tool we faced above issue.<\/p>\n

Solution:<\/strong><\/p>\n

We did some testing and found that the Major and Minor versions of a plugin assembly cannot be changed.<\/p>\n

Conclusion:<\/strong><\/p>\n

If you have a plugin registered in production, manage the version by updating the build number or revision part of the version # or you will need to unregister and register it again.<\/p>\n

QuickBooks Integration with Dynamics 365\/CRM – Get the Best of Both Worlds with InoLink!<\/i><\/b><\/span><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

Introduction: Plugin Assemblies are versioned and need to be signed with a strong key for them to be registered to Dynamics CRM. Any update to the library and compiling the project may cause the version # to change or to maintain versioning practices you may decide to change the version # and this can cause\u2026 Read More: Watch out for Issues with Version & Updating Plug-in assembly\u2026 »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":4566,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16,19,42],"tags":[567,669,1328,1329],"class_list":["post-4567","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dynamics-365","category-dynamics-crm","category-plugin","tag-dynamics-365-plugin","tag-dynamics-crm-plugin","tag-plugin-registration-tool-for-dynamics-365","tag-plugin-registration-tool-for-dynamics-crm"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t