Deploying a Revit Plug-in

[ericanastas]

Does anyone have any good examples of how to deploy a Revit plug-in (ExternalApplication)? Specifically I'd like to know the best way to deal with changing paths to either the ribbon button images, and or the DLLs which contain the IExternalCommand classes.

I figure I could use System.Reflection.Assembly.GetExecutingAssembly(), to find the location of the currently executing assembly and then either put all the Commands in the same file as the External Application classes, or know where to find any other files relative to this path.

Is this the best or at least typical way this is done?

[Anonymous]

Since all methods require a change to the Revit.ini file, the easiest package is the application, vs the many commands. Then the application can define the commands as it sees fit. A method last used by me was to create a routine that would read an xml file (a modification to the example shown in the sample loader: 'RvtSamples'). This way, to add, remove or change a command, you only needed to modify the xml file. Then place a main loader dll in the same place for the revit.ini file to find. After that it is up to your xml file to determine where each command is. And yes, using reflection to find where the current app dll is located worked great for me too.

jvj

[Anonymous]

I am using a WIX installer to modify previous application deployments. This updates/appends the revit.ini but also can overwrite existing installations of application .txt. files read from toolbars like RvtSamples.

great tutorial with files @ http://goo.gl/FEat

alan