All registered plugin steps are deleted every time the Plugin assembly is updated

(0) Share

Report

Posted on by ALTOSHAAM

180

Hello,

I've faced a strange issue during migration of existing functionality from current production version (8.2.2) to the latest one (9.0.2).

I've updated CRM SDK packages references in the plugin project to the latest available version (9.0.2.3). Project is building without any issue.

I've downloaded latest Plugin Registration Tool from NuGet (https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool/9.0.2.3), which is compatible with CRM 9.0.

But, when I'm updating the plugin assembly in CRM all plugin steps dissapear. So it seems, I need to re-create them after each Plugin DLL update.

Does anyone faced the same issue during migration and found some solution for it?

Thanks in advance!

Regards,

Anton

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (1)

gdas 50,091 Moderator on at

Like (0)

Report

Hi ,

Could you please download the sdk from below reference and open plugin registration tool from there.

http://xrm.tools/SDK

Was this reply helpful? Yes No
Verified answer

ALTOSHAAM 180 on at

Like (0)

Report

Hi Goutam,

Thanks for reply.

I've tried version 9.0.0.9314 from the link you've provided, but with no luck - result is the same.

But during my experiments, I've found that revision and build numbers are generated automatically by VS during build.

So, I assume the root cause is in assembly versioning.

When I've tried to use the same version all the time - all is working fine - assembly is updated in place, and all steps remain untouched.

When I'm changing the build number (for example, from 2.0.0.0 to 2.0.0.1) - than it treats it as brand new assembly and recreates it in CRM - and all registered steps are dropped.

Previous version of Plugin Tool/CRM treated release and build version change as in-place upgrade. And only major/minor version change was treated as full assembly replacement.

--

Regards,

Anton

Was this reply helpful? Yes No
Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

This might be trivial, but I just want to make sure that when you update the assembly, are you checking the list of Steps that are going to be as part of this solution...

Was this reply helpful? Yes No
ALTOSHAAM 180 on at

Like (0)

Report

Hi Aric,

Absolutely, I'm selecting all plugins available in the assembly during update.

Actually, you can select plugins (.NET classes that implement IPlugin functionality) in the tool, but not the steps, which are just metadata records in the CRM database.

--

Regards,

Anton

Was this reply helpful? Yes No
Temmy Wahyu Raharjo 2,916 on at

Like (0)

Report

Hi, instead of create manual. Why not registered using crm package? So when deployed, you only need to deploy from vs and it will records all of your step in 1 file. It's a bit strange but I believe it because of assembly version number.

Was this reply helpful? Yes No
Michael Saroka 60 on at

Like (0)

Report

How do you deploy a package from VS? I was under the impression that the only way to make a package was to export a solution from the web UI.

Was this reply helpful? Yes No
ALTOSHAAM 180 on at

Like (0)

Report

Probably, there is some VS extension, which could perform solution packaging and deployment. But I'm not aware of details.

Such kind of deployment is applicable for development environment or for small projects. But it becomes mostly unusable when you have few staging environments, all CRM customizations committed into source control and CI tuned up.

Was this reply helpful? Yes No
Alex Fun Wei Jie 33,628 on at

Like (1)

Report

Hi Michael,

you can refer below articles on how to achieve it using developer toolkit.

community.dynamics.com/.../install-dynamics-365-developer-toolkit-with-visual-studio-2017

community.dynamics.com/.../microsoft-dynamics-365-developer-toolkit-configuration

Although this is crm 2013, but the step is roughly the same.

us.hitachi-solutions.com/.../using-the-microsoft-crm-developer-toolkit-to-deploy-custom-plugin-assemblies

Was this reply helpful? Yes No
Michael Saroka 60 on at

Like (0)

Report

Thanks Wei Jie Fun. This is super helpful. It does not like the new SDK as it seems ver 8 is hardcoded into the backend. But everything else seems to work.

Was this reply helpful? Yes No