What the addin registration file look like

If all default settings except for the addin name are accepted, the content of the resulting AddIn registration/manifest file will look like the following:

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

<RevitAddIns>

     <AddIn Type="Application">    <Assembly>C:\Temp\WizardTest\WizardTest\bin\Debug\WizardTest.dll</Assembly>

          <FullClassName>WizardTest.ExtApp</FullClassName>

          <ClientId>16182402-7761-437a-a22d-285bf114fd2b</ClientId>

          <Name>WizardTest</Name>

     </AddIn>

</RevitAddIns> 

If the setting of the Add into menu is opted for the external command and a few command invisibility modes have been chosen, one more AddIn element will be added to the root RevitAddIns node:

     <AddIn Type="Command">

          <Assembly>C:\Temp\WizardTest\WizardTest\bin\Debug\WizardTest.dll</Assembly>

          <FullClassName>WizardTest.ExtCmd</FullClassName>

          <ClientId>32ebacd0-bbb7-4667-bb2e-54a2cd137cab</ClientId>

          <Text>Command ExtCmd</Text>

          <Description>The command ExtCmd</Description>

          <VisibilityMode>NotVisibleInFamily</VisibilityMode>

          <VisibilityMode>NotVisibleWhenNoActiveDocument</VisibilityMode>

          <VisibilityMode>NotVisibleInMechanical</VisibilityMode>

     </AddIn> 

The assembly path, full class name, client id, description, etc. are all filled out automatically. In addition, the manifest file will be put into the user roaming folder, and a link to the file as well as a local copy will be added to the project.

All the content of the above manifest files were created automatically by the RevitAddinWizard.