0

How can a new workflow class be added to an existing assembly that has already been registered and contains custom workflow activities that are already being used by workflows?

I often register an assembly with a workflow activity and then later want to add more classes.

The only way that has worked for me is to de-register and re-register the assembly, otherwise the custom workflow activity does not show up in the workflow designer; this approach is not ideal as it involves removing steps from all the workflows that use the assembly.

HenricF
  • 218
  • 3
  • 19
Bvrce
  • 2,170
  • 2
  • 27
  • 45

1 Answers1

2

After you add the new CodeActivity inside the existing workflow assembly you need to update the assembly using the Plugin Registration Tool. By default the new classes will not be selected, but you can select them and the Plugin Registration Tool will include them. It is not necessary to unregister and register again the dll.

A good practice is to change the Assembly Version and File Version inside the project properties before compile (for example from 1.0.0.0 to 1.0.0.1) , it will force the CRM service to use the just updated assembly (and the designer will see the new activities)

Guido Preite
  • 14,905
  • 4
  • 36
  • 65
  • If I change the major or minor version number (from 1.0.0.0 to 2.0.0.0 or 1.0.0.0 to 1.1.0.0) the registration fails. It seems that the only way to change the major or minor version is to register a new assembly. What you have suggested works as changing the build or revision number shows the new workflows in the workflow designer. – Bvrce Feb 04 '14 at 17:51