locked
WF4.5 Versioning WorkflowServiceHost RRS feed

  • Question

  • Hello, we are currently in the final stages of developing our first Workflow Solution and are looking at implementing side-by-side versioning.

    We have achieved this successfully with the standard DefinitionIdentity / App_Code approach and persisted instances within the AppFabric database are showing as running against our versioned workflows however we have another issue.

    As part of our solution in VS2012 we have a seperate project to our main workflow service that contains a number of custom activities (both XAML designer and CS code) that are subsequently inherited by the main XAMLX workflow.

    The problem we have is that we are unable to associate the compiled assembly of these custom activities to our main versioned workflow, are there any suggestions as to how to do this as we currently host the workflow using IIS/AppFabric and the WorkflowServiceHost?

    Friday, May 24, 2013 11:34 AM

All replies

  • Jon,

    Appreciate this is quite an old thread, but did you manage to come with a solution. We have a similar scenario and the only possible solution I can see for this is signing the compiled assemblies and either using GAC for side by side versioning or hosting the compiled assemblies in custom location and then listening to the Assembly Resolve event.

    Would be interested if there is a better way to achieve the same.


    Tuesday, February 2, 2016 4:47 PM