You’re offline. This is a read only version of the page.
105
Hi Experts,
I have a assembly(.dll) which contains 3 custom workflow activity steps under it. I have changed the code for one of the programs for one of the custom workflows, but when I compile the .dll created, contains the code for the changed module + the other modules as well.
I've registered this assembly using the registration tool in Dev, and during that, i had checked update all the steps for updating the other workflow activities, even though they weren't changed.
So now when i need to move this change to test and prod, via a solution, do I only need to include only the Plugin-assemblies component, or do I need to also include the SDK message Processing Steps too ? (these already exist in test & prod). As, my change was an update to the code and I haven't introduced a new module in the assembly.
Hi Andreas,
Thank you for your response to my post.
The change I've made is in the logic for a bug fix. I haven't changed the input/output parameters of the custom workflow activity.
So it seems to me, that the below section of the first link you shared is relevant in my case:
Update a custom workflow activity
You might want to update your existing workflow activities to fix some bugs or to make changes in some of the private code implementation. When updating a custom workflow activity, make sure that you do not make significant changes in the public classes or method signatures in the underlying code, such as changing the input parameters, because this might break existing workflow instances that use the custom workflow activity.
Make necessary changes in the underlying code of the custom workflow activity.
Change the values for <build_number> and <revision> only in the assembly information of the custom workflow activity, and compile it. For example, change the value of your assembly from “1.0.0.0” to “1.0.10.5”.
Update your registered custom workflow activity in Dynamics 365 with the new assembly.
After updating the custom workflow activity in Dynamics 365, all existing running process (workflows and dialogs) instances that are using the custom workflow activity will automatically start using the updated activity without requiring you to update the process definitions.
I've created a new solution with version 1.0.0.0 and added the existing assembly in it. Do I need to change the build and revision number for the assembly before I move it to Test and Prod, and if so, how can I go about doing that?
Thanks.
Thank you Mahender for your response. I have now only included the .dll file now in my Solution.
Mahender is right, but also consider what happens if you apply assembly versioning:
docs.microsoft.com/.../update-custom-workflow-activity-using-assembly-versioning
Hi,
You just need to move whatever you changes, so if you changed only assembly code and there is no changes on the registration steps, you don't need to redeploy steps, just include your assembly in your solution for deployment.
Share
Report
All responses (
Answers (
