Load Multiple ExternalCommand with Different Version Numbers

[jinsol.kim]

Hi, 

I usally load the same external command with two different versions at the same time, one in a custom tab, another in the Add-ins tab. 

When I loaded the external command, I saw only one version was loaded and the first loaded version seemed to suppress the other.

So the two seperate command buttons run one singular verision of command whatever loaded first. Can you tell me how I can load two different versions of External Command? Should I make something different other than version number?

Please let me know. Thanks,

Jinsol

[Aaron.Lu · Accepted solution]

Dear Jinsol,

I can reproduce your problem, and I think currently there is no workaround for it unless you use different names of the ExternalCommand

I'm still consulting with engineering team, once I got answer I will let you know.

[Aaron.Lu]

Another workaround is using AddinManager to load your external command, it supports loading multiple same assemblies in different folder.

[jinsol.kim · Accepted solution]

The different assembly names of the external command will be used in PushbuttonData to combine different dlls into one Ribbon panel. 

I've also searched a little bit,but the renaming dll seems to be the only solution I have. 

Thank you, Aaron. 

[Aaron.Lu]

Dear jinsol,

Just to confirm that renaming dll won't work, but renaming namespace or class name will work.

Do you agree with that?

[jinsol.kim]

Hi Aaron,

I changed the name of the assembly keeping the name space same and build the Visual Studio project. It seems to work in that way.
Thanks,

Jinsol

[Aaron.Lu]

Thanks for letting me know.

You still registering an External Application and an External Command?

unfortunately, It can't work from my side..

[jinsol.kim]

Yes. I've registered external commands with all different names of dlls depending on their version numbers, for example xxx_v2015.0.1.0.dll
The name should be changed from the assembly in Visual Studio instead of simply renaming the name of the dll file.

[Aaron.Lu]

Exactly!!!

1. Renaming the class name or namespace won't work if we simply rename or relocate the dll files

2. Renaming the "Assembly name" in visual studio and rebuild will work!

Thanks very much for your information!