Assemblies and Script Steps

asked on June 23, 2017

Based on our experience so far, it appears that we are unable to deploy a new Assembly file to the GAC without going into the script steps (by workflow map) and rebuilding the References. For example, we deploy a new assembly file to the GAC (v1.0.0 to v1.0.5) and have to go into the script step in a workflow and delete and add back the reference. Is that expected behavior?

Assuming that's expected, if we were to use the same version number, is there a way to refresh the loaded assembly? We came across some issues earlier which did not detect the recent code pushed under an existing version.

Any additional information or recommendation on how to deploy, version and maintain new assembly files is appreciated.

0 0

SELECTED ANSWER

replied on June 26, 2017

This is expected behavior for .Net. Changing the assembly version usually means architectural changes were made that may not be backwards compatible. So a deliberate update of scripts and applications using the old version is expected. If no breaking changes were made, then the assembly version should be left unchanged and only the file version should be updated.

1 0

replied on June 26, 2017

Thank you for the reply Miruna. Assuming no assembly version change, would you be able to outline the procedures to update the file version? I just want to be sure we have the steps outlined as in the past it seems like the updated DLL was not loaded with future workflow instances.

0 0

Question

Question

Answer

Replies

Sign in to reply to this post.