The Revit API offers the ability to register API applications via a .addin manifest file.
Manifest files will be read automatically by Revit when they are places in one of two locations on a user's system:
All files named .addin in these locations will be read and processed by Revit during startup.
A basic file adding one ExternalCommand looks like this:
Code Region: Basic manifest file for an ExternalCommand |
---|
<?xml version="1.0" encoding="utf-16" standalone="no"?> <RevitAddIns> <AddIn Type="Command"> <Assembly>c:\MyProgram\MyProgram.dll</Assembly> <AddInId>76eb700a-2c85-4888-a78d-31429ecae9ed</AddInId> <FullClassName>Revit.Samples.SampleCommand</FullClassName> <Text>Sample command</Text> <VisibilityMode>NotVisibleInFamily</VisibilityMode> <VisibilityMode>NotVisibleInMEP</VisibilityMode> <AvailabilityClassName>Revit.Samples.SampleAccessibilityCheck </AvailabilityClassName> </AddIn> </RevitAddIns> |
A basic file adding one ExternalApplication looks like this:
Code Region: Basic manifest file for an ExternalApplication |
---|
<?xml version="1.0" encoding="utf-16" standalone="no"?> <RevitAddIns> <AddIn Type="Application"> <Name>My sample application</Name> <Assembly>c:\MyProgram\MyProgram.dll</Assembly> <AddInId>604B1052-F742-4951-8576-C261D1993107</AddInId> <FullClassName>Revit.Samples.SampleApplication</FullClassName> </AddIn> </RevitAddIns> |
Multiple AddIn elements may be provided in a single manifest file.
See Add-in Registrationfor more information on the available XML tags for .addin files.