I re-hosted the workflow designer in a standalone application. Is there a way to force the designer to not include the version of the Assembly containing my custom activities.
What is happening is that my custom activity assembly version changes quite often. Thus, my rehosted designer throw an exception since the version in the xoml is in version A. And now my custom activity assembly is in Version B.
My re-hosted designer compiles with my custom assembly so any changes to the version of my custom assembly will break my workflows. The only way to make it work is to open it in the XML editor and to manually change the version to B. Hope that clears things up.
Basically, I’m wondering when serializing into xml, if it’s possible to not include the Version of the custom assembly??? Is this possible ?
Not sure if this helps your problem but this blog post describes how to use multiple versions of an assembly side by side.
Other that that you might decide not to use a strongly named assembly or update the version number so .NET versioning doesn’t come into play