Note that there are some explanatory texts on larger screens.

plurals
  1. PODo you have to strongly name assemblies to run multiple versions of the same assembly in WF?
    primarykey
    data
    text
    <p>I'm having to maintain a system running windows workflow foundation, changes need to be made to the Workflows so I'm developing them in a new version of the workflow project, say Version 2.0.0.0</p> <p>I need to run Version 1.0.0.0 workflows, at the same time as Version 2.0.0.0 workflows, with new workflows being created using the latest assembly.</p> <p>I've read <a href="http://msmvps.com/blogs/theproblemsolver/archive/2008/09/10/versioning-long-running-workfows.aspx" rel="nofollow">this great explanation</a> on running multiple versions of workflows, and within my app.config I have the following:</p> <pre><code>&lt;runtime&gt; &lt;assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"&gt; &lt;dependentAssembly&gt; &lt;assemblyIdentity name="some.namespace.workflow" publicKeyToken="null" /&gt; &lt;codeBase version="1.0.0.0" href="legacy/version_1_0_0_0/some.namespace.workflow.dll"/&gt; &lt;/dependentAssembly&gt; &lt;/assemblyBinding&gt; &lt;/runtime&gt; </code></pre> <p>However, the new workflows always get created with version 1.0.0.0 - even though I've changed the version of the related Workflow project to 2.0.0.0</p> <p>The only difference I can see is that my assemblies aren't strongly named, could this be what's causing it?</p> <p>Thank you.</p> <p>UPDATE:</p> <p>I think this problem might be related to the way I'm loading the assembly by using:</p> <pre><code>Assembly asm = Assembly.Load("some.namespace.workflow"); </code></pre> <p><a href="http://blogs.msdn.com/b/rjacobs/archive/2011/01/12/assembly-load-version-numbers-and-unsigned-assemblies.aspx" rel="nofollow">This chap</a> is suggesting that you need to strong name your assemblies to use the <code>Assembly.Load</code> method - is this true?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload