This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 95
Add in naming conventions
slluis edited this page Nov 20, 2014
·
2 revisions
Home > Reference Manual > Description of Add ins and Add in Roots > Add in naming conventions |
---|
Looking at the previous example it may seem a bit strange to use the identifier "Core" for an add-in root, however it makes a sense when used together with a namespace. The full ID of an add-in is the concatenation of the namespace and the id, so the full ID would be "TextEditor.Core".
All add-ins extending the an add-in root should use the same namespace. So for example, we would have "TextEditor.XmlAddin", "TextEditor.CompilerService", etc.
The following declaration would be valid for an add-in:
<Addin namespace="TextEditor">
...
</Addin>
IDs are not mandatory if the add-in can't be extended. Specifying the namespace is also not mandatory, but very convenient to make it clear what's the scope of the add-in.
- Extension Points and Extensions
- Querying Extension Points
- Type Extension Metadata
- Data-only Extension Points
- Data Files and Resources
- About Lazy Loading
- Thread Safety
- The Add-in Registry
- Addin Discovery
- Creating and Managing Add-in Packages
- Advanced Concepts