This article covers the following aspects:
- App Identifier concept
- Use of the App Identifier
- Developing for another company
- Validation upon App version registration
App Identifier concept
Upon App registration, a unique App Identifier is automatically generated and visible within the feedback information provided by the App validation tool (i.e. on top).
It consists out of the Manufacturer Code identifying the KNX Member company owning the ETS App in question plus a unique identifier starting with 'A'. In this example: 'M00FA' is the Manufacturer Code of KNX Association and 'A0005' is the unique identifier.
Use of the App Identifier
The App Identifier shall be used as return value in the App source code:
And it shall also be used in the AddInManifest.xml file of the App:
Developing for another company
In case a developer from company A should develop an App for another company B, then company B should apply for App developer status and register a new App. The App Identifier of this new App should be given to the developer of company A. Furthermore, the new App for company B must have a different assembly name and a different namespace than the App from company A.
Validation upon App version registration
Upon App version registration, the App validation tool of MyKNX compares the App Identifier that is used in the source code and in the AddInManifest.xml with the given App Identifier upon App registration. In case of inconsistencies, the validation tool will return an error message like e.g. this one:
