Assembly Caching Issue in Dynamics 365 V9 - Update Assembly Version of Custom Workflow Steps With PowerShell

As Alex blogged we are currently facing a caching bug of plugin assemblies in Dynamics 365 cloud instances (V9). You can do an in-place upgrade with Plugin Registration Tool without an exception now (see Unable to in-place update plugin in Dynamics 365 (with build or revision number changed) but for some assemblies it just won’t propagate to your workflow definitions. In the past we could fix it by clicking a save button in Properties tab of the assembly in Plugin Registration Tool but this does not work anymore in V9. I have put together another workaround which is usable in release automation scenarios. !](//uploads7/2018/07/Update-AssemblyUsageToLatestVersion.gif)   You can use this when moving solutions between environments (unfortunately I had no luck with importing it back to the origin environment). The most common situation is exporting an unmanaged solution as managed from a sandbox to a production environment.

1. Follow the instructions here and install a PowerShell module: https://github.com/TheNetworg/dynamics365-release-automation-tools/blob/master/README.md
2. Then include the desired version of assembly in the solution.
3. Export your solution. Both Managed and Unmanaged are supported.
4. From the folder where you downloaded the solution open a PowerShell console.
5. Run Update-AssemblyUsageToLatestVersion cmdlet with a path parameter.
6. Check the result.
7. Now you can take the ZIP file which has been modified and import it to the target environment. If there was an older version of the plugin and solution, it will be updated.