Hi,
They are loaded in alpabetical order. I have a boot-strap addin named "AAA_..." which works well. There was a previous disussion here:
running-add-ins-from-a-network-drive
Summary form above:
If you are worried about whether the loading order of the addins can be relied upon, the good news is that it is a documented feature and is well defined. I make use of this myself and was at first a little dubious about its long-term reliability so I searched a little and found this in the Developers Guide:
All files named .addin in these locations will be read and processed by Revit during startup. All of the files in both the user-specific location and the all users location are considered together and loaded in alphabetical order. If an all users manifest file shares the same name with a user-specific manifest file, the all users manifest file is ignored. Within each manifest file, the external commands and external applications are loaded in the order in which they are listed.
Full details Here.
It's funny that I didn't know this earlier, but I guess once you learn how to build manifest files (usually by example), you never really look at that section of the guide and miss out on these little gems of important information.
______________
Yes, I'm Satoshi.
