API 2012 Support: Revit Manifest Organizer – III

As announced before, Revit Addin Wizard (RevitAddinWizard) and its various wizards, coders and widgets have supported Revit API 2012 additionally natively and seamlessly.

In this post, let us have a look at how to find the missing VendorId nodes in Revit manifest addin files using Revit Manifest Organizer. If Version 2012 is selected and the Check Integrity is run, the VendorId nodes will be inspected in all the available manifest addin files. In case, any VendorId nodes are missing, the problems will be reported on the status bar against the Application or Command types of the Revit manifest addin files such as the cccc.AddIn file as shown in the following screenshot:

 
If we look at the manifest addin file using View Selected or Edit Selected, we may find it looks like:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<RevitAddIns>
  <AddIn Type="Application">
    <Assembly>C:\Temp\RevitAddin30\bin\Debug\RevitAddin30.dll</Assembly>
    <FullClassName>RevitAddin30.ExtApp</FullClassName>
    <ClientId>8f0fbb84-d61c-4e5b-bf8b-fe91334178ed</ClientId>
    <Name>RevitAddin30</Name>
  </AddIn>
  …
  …
</RevitAddIns>

As can be noticed, it misses out the VendorId node. The issue can be due to many reasons, one of which may be the file is from an early version addin project, another may be the VendorId is neglected when the manifest file is created manually. By the way, if a Revit 2012 addin project is created using the latest build of Revit Addin Wizard (RevitAddinWizard) with the proper version selected, its manifest addin file will be created correctly, intelligently and automatically.

Then we can check off the item in the left pane and press the Add Missing VendorId button to fix the problem:

Please note that the Add Missing VendorId feature will only be available when Version 2012 is selected, some missing VendorId cases are there, and at least one of such problematic manifest addin files is checked off.

As mentioned previously, the VendorId as shown in the Other Options dialog will be used to fix any missing VendorId problems. The following dialog will appear to double check on this:

 
After the manifest addin file is fixed, it may look like the following now:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<RevitAddIns>
  <AddIn Type="Application">
    <Assembly>C:\Temp\RevitAddin30\bin\Debug\RevitAddin30.dll</Assembly>
    <FullClassName>RevitAddin30.ExtApp</FullClassName>
    <ClientId>8f0fbb84-d61c-4e5b-bf8b-fe91334178ed</ClientId>
    <Name>RevitAddin30</Name>
    <VendorId>ABC</VendorId>
  </AddIn>
  …
  …
</RevitAddIns>

If some other VendorId is better to use, please reset it in the same Other Options (Miscellaneous) dialog.

Revit Addin Wizard (RevitAddinWizard) and its various wizards, coders and widgets have supported Revit API 2012 additionally natively and seamlessly.