Hi,
I was after a bit of help to understand the manifest file (.addin) a bit better.
When do you use <AddIn Type="Application"> and when <AddIn Type="Command">
If you have a solution that contains multiple commands (see example below), what is the best approach?
in this example on youtube https://youtu.be/QiFa4o5eQ3c?si=E2e94RUVB5KPgajf , as you can see there are four separate commands, linked to buttons in the Application.cs
in this case, do you just create a manifest and used the Application.cs in the class name?
I have also seen manifest file that have both <AddIn Type="Application"> and <AddIn Type="Command"> in them! when do you use one like this?
Thanks for your help and support
Solved! Go to Solution.
Hi,
I was after a bit of help to understand the manifest file (.addin) a bit better.
When do you use <AddIn Type="Application"> and when <AddIn Type="Command">
If you have a solution that contains multiple commands (see example below), what is the best approach?
in this example on youtube https://youtu.be/QiFa4o5eQ3c?si=E2e94RUVB5KPgajf , as you can see there are four separate commands, linked to buttons in the Application.cs
in this case, do you just create a manifest and used the Application.cs in the class name?
I have also seen manifest file that have both <AddIn Type="Application"> and <AddIn Type="Command"> in them! when do you use one like this?
Thanks for your help and support
Solved! Go to Solution.
Solved by Mohamed_Arshad. Go to Solution.
Application do somethings OnStartup, OnShutdown (start and close Revit).
If you already create buttons (or other ways) for a command in application. There is not need to put your command in .addin file again.
------
When you put a command in .addin. It can be called by "Add-Ins" tab -> External Tools -> Name(defined in <Text>Name</Text>).
------
And the separated .cs file in C# is only for human read easier.
If you want, writing app and command in some .cs file is fine, too.
Application do somethings OnStartup, OnShutdown (start and close Revit).
If you already create buttons (or other ways) for a command in application. There is not need to put your command in .addin file again.
------
When you put a command in .addin. It can be called by "Add-Ins" tab -> External Tools -> Name(defined in <Text>Name</Text>).
------
And the separated .cs file in C# is only for human read easier.
If you want, writing app and command in some .cs file is fine, too.
Hi @MOR75669
In Revit API we have two major Interfaces IExternalCommand and IExternalApplication we can understand these two interface in simple way.
IExternalApplication => Front end of the Revit User Interface (ex. Button).
IExternalCommand =>Backend of the Revit User Interface (ex. Button's backend code).
Kindly check the below Image for detail explanation.
Complete Workflow
Hope this will Helps 🙂
Hi @MOR75669
In Revit API we have two major Interfaces IExternalCommand and IExternalApplication we can understand these two interface in simple way.
IExternalApplication => Front end of the Revit User Interface (ex. Button).
IExternalCommand =>Backend of the Revit User Interface (ex. Button's backend code).
Kindly check the below Image for detail explanation.
Complete Workflow
Hope this will Helps 🙂
Can't find what you're looking for? Ask the community or share your knowledge.