As announced previously, 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 the Command Manifest Creator Wizard. Its wizard pages are the same as before. The only difference is that for external commands of Revit addin projects of version 2012 the VendorId node will be created into the resultant addin manifest (.AddIn) file.
<?xml version="1.0" encoding="utf-8"?>
<RevitAddIns>
<AddIn Type="Command">
<Assembly>C:\Temp\RevitAddinCS1\RevitAddinCS1\bin\Debug\RevitAddinCS1.dll</Assembly>
<FullClassName>RevitAddinCS1.ExtCmd</FullClassName>
<ClientId>fbe2bb45-60e8-402f-88e5-1d75b37f1559</ClientId>
<Text>RevitAddinCS1.ExtCmd</Text>
<Description>Desctiption of CmdManifestCreator</Description>
<VendorId>ABC</VendorId>
<VisibilityMode>NotVisibleInStructure</VisibilityMode>
<VisibilityMode>NotVisibleInMEP</VisibilityMode>
</AddIn>
</RevitAddIns>
The VendorId is retrieved from the RevitAddinWizard settings automatically and intelligently. So if the VendorId is not wanted yet at this moment, it can either be changed automatically from next time on after it’s reset in the RevitAddinWizard pages or updated manually.
Revit Addin Wizard (RevitAddinWizard) and its various wizards, coders and widgets have supported Revit API 2012 additionally natively and seamlessly.
Recent Comments