I cannot count the number of times I have pointed out that the Copy Local flag should be set to false on the Revit API assembly references.
Here are some of the numerous previous examples and explanations of this:
<!–
006_sdk_samples_solution.htm:'Copy Local' flag maintained by
006_sdk_samples_solution.htm:and at the same time the existi
008_debugging.htm:
008_debugging.htm:
024_application_events_vb.htm:
159_export_instance_to_gbxml.htm:
159_export_instance_to_gbxml.htm:
<
h4>Set Copy Local to False
159_export_instance_to_gbxml.htm:
Always ensure that the C
189_porting_to_vb.htm:
268_custom_ribbon_tab.htm:As always, we need to remember to
310_reload_addin.htm:
By the way, in this sample, the Revi
360_p2c.htm:
Almost all Revit add-ins will need to referen
415_devtv_addin_templates.htm:
443_idling_selection_watcher.htm:
459_cpp_addin.htm:
Don’t forget to set the Copy Local flag
–>
- A C++ Revit add-in
- Selection watcher using Idling event
- The DevTV add-in templates
- Pipe to conduit converter
- Custom ribbon tab
- Porting from C# to VB.NET
- Exporting a family instance to gbXML
- Application events in VB
- Debugging a Revit add-in
- The SDK samples solution
This flag appears in the properties of the Revit API references.
It is also displayed in the list of the references themselves in a VB project.
Here they are set to True, which is what we want to avoid:
In a C# project, you can right click on the Revit API references in the Visual Studio solution explorer and selecting its properties in the context menu to see and modify its current setting:
You can toggle this property with a double click.
If this flag is set to True, Visual Studio will create local copies of RevitAPI.dll and RevitAPIUI.dll when compiling the plug-in and use these copies when loading them.
This confuses the debugger and Revit when running the add-in, as well as unnecessarily polluting your hard disk with copies of this multi-MB file.
To avoid having to reset this property when modifying an existing reference, for instance when migrating to a new version of the Revit API, do not delete the existing reference.
Instead, simply add the new reference to the current assembly to overwrite the old one.
The old, existing data will be updated, the new path will be stored, and the existing ‘Copy Local’ setting will be preserved.
By the way, the same applies to the
AutoCAD.NET assemblies.
At least this post gives me a completely comprehensive description to refer to next time I have to point this out…
Leave a Reply