Load multiple assembly version of plugin in Revit 2013

Load multiple assembly version of plugin in Revit 2013

sankar_g
Enthusiast Enthusiast
1,032 Views
4 Replies
Message 1 of 5

Load multiple assembly version of plugin in Revit 2013

sankar_g
Enthusiast
Enthusiast

Hi..

 

   Is it possible to load multiple assembly version of plugin in Revit 2013. If possible, Please give steps to follow

 

 

Thanks in Advance,

sangsen

0 Likes
1,033 Views
4 Replies
Replies (4)
Message 2 of 5

Joe.Ye
Alumni
Alumni

 

Revit  allow to load addins of diverse versions. I just tested to load 2 versions of a simple Revit dll.

This needs the following condition.

In the load setting file, for same command, has different GUID string.

 

Hope this helps



Joe Ye
Contractor
Developer Technical Services
Autodesk Developer Network
0 Likes
Message 3 of 5

sankar_g
Enthusiast
Enthusiast

Hi Joe Ye,

 

    Thanks for your response.

     load settings file mean? I assumed it as addin file.

 

External Command :

                 I am also tested with 2 version of simple dll with different GUID in addin file. In Revit two versions are loaded without any load error. But it execute only first version code for both command.

 

External Application:

             Revit throws load error as Ribbon Tab name should be unique when we try to load two version of dll.

 

 

My requirement is to install development and release version of a product in revit.

 

Thanks,

sangsen

 

 

 

0 Likes
Message 4 of 5

Joe.Ye
Alumni
Alumni

 

Hi Sangsen,

 

Thanks for your update.

How did you start your external  commands?  via the Ribbon buttons?

 

I loaded the same commands from two dlls via addin file. Thw two identical commands will show in the external tools drop list in Add-ins Tab with different name. 

Here is the addin file. The name shows in the drop list is different: one is HelloWorld_New, the other is HelloWorld.

 

<?xml version="1.0" encoding="utf-8"?>

 <RevitAddIns>

<AddIn Type="Command">
<Assembly>C:\test\HelloWorld\HelloWorld\bin\Debug\HelloWorld.dll</Assembly>
<ClientId>a63fafe7-690b-413c-a9e3-efdbaa0971c2</ClientId>
<FullClassName>HelloWorld</FullClassName>
<Text>HelloWorld</Text>
<Description>""</Description>
<VisibilityMode>AlwaysVisible</VisibilityMode>
<VendorId>ADSK</VendorId>
<VendorDescription>Autodesk, www.autodesk.com</VendorDescription>
</AddIn>
<AddIn Type="Command">
<Assembly>C:\test\HelloWorld\HelloWorld\bin\HelloWorld.dll</Assembly>
<ClientId>a562d3cb-e06a-4ad6-b2b7-e57b9b63618f</ClientId>
<FullClassName>HelloWorld</FullClassName>
<Text>HelloWorld_New</Text>
<Description>""</Description>
<VisibilityMode>AlwaysVisible</VisibilityMode>
<VendorId>ADSK</VendorId>
<VendorDescription>Autodesk, www.autodesk.com</VendorDescription>
</AddIn>
</RevitAddIns>

 

And the two commands' content is a little different on a string. 

These two commands can started their own external commands, the they can show different task dialogs.

 

Not sure how you start the two commands? By clicking the Ribbon buttons?

 

For external applications, for the Tab name, you need to assign different name for the two versions. Revit doesn't allow the duplicate name. In each external application, bound its buttons to the right dll.  I think this should work.

 

 


______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

 



Joe Ye
Contractor
Developer Technical Services
Autodesk Developer Network
0 Likes
Message 5 of 5

sankar_g
Enthusiast
Enthusiast

Hi joe,

 

       Thanks for your update.

       I am also started external commads via external tools dropdown only. I tried with two version of solutions to display current executing assemby version info in dialog. In the code I just changed the build number in assembly info.cs.

The commands shows different dialog with different dialog title but i found that the dialog message (To display executing Assembly version) are same. Please suggest any solutions to run the commands without any issue.

 

 Can signing the Assembly with key solve External Application ribbonTab name problem?

 

Thanks

sangsen

0 Likes