topic Re: Revit Add-in runs in debug but not standalone. in Revit API Forum

Revit Add-in runs in debug but not standalone.

konstantin.udilovich — Mon, 09 Sep 2019 13:31:04 GMT

Hi,

I am observing a strange behavior. My IExternalApplication loads correctly and configures the buttons on the ribbon when I run it in Debug mode, by starting Revit as an external program from Visual Studio. At the compile time, the files are copied automatically into the Addin folder. When I close the Visual Studio and start Revit from a shortcut the app crashes when it tries to add a button to a ribbon. The contents of the Addin folder is the same. I have checked that both VS and the desktop icon point to the same Revit.exe. What could be the difference in running an app in debug mode versus standalone Revit?

Additional information: I do use Managed Compatibility Mode in Visual Studio debug settings.

Re: Revit Add-in runs in debug but not standalone.

jeremytammik — Mon, 09 Sep 2019 19:28:53 GMT

Is 'Copy Local' set to false on the Revit API assemblies?

https://thebuildingcoder.typepad.com/blog/2011/08/set-copy-local-to-false.html

Re: Revit Add-in runs in debug but not standalone.

konstantin.udilovich — Mon, 09 Sep 2019 19:35:30 GMT

Thanks for your response Jeremy. Yes, CopyLocal was set to false. Looks like I figured this one out. The problem was that for the AssemblyName parameter I used just the file name. Revit wanted to have a full path. This did the trick:

var fileName = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), @"Autodesk\Revit\Addins\2018\MyAddins.dll");
PushButtonData button1 = new PushButtonData("MyButton", "Export model data",fileName, "MyExportCommand");

I am still puzzled why it was working in Debug mode, but I need a full path when Visual Studio is not present ....

Thanks again.