ServiceId
Identifies the service for a contact action.
Element hierarchy
- <Extension>
-
- <Contact>
-
- <ContactLaunchActions>
-
- <LaunchAction>
- <ServiceId>
Syntax
<ServiceId>
Identifies the service for a contact.
</ServiceId>
Attributes and Elements
Attributes
None.
Child Elements
None.
Parent Elements
Parent Element | Description |
---|---|
LaunchAction (in ContactLaunchActions) | Describes a ContactLaunchActions content action. |
Remarks
The ServiceId definition has these statements:
<xs:complexType name="CT_ServiceId" mixed="true">
<xs:simpleContent>
<xs:extension base="ST_ServiceId">
<xs:attributeGroup ref="m:ExtensionBaseAttributes"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
The preceding 'ref' statement indicates that ServiceId inherits all of these Extension base attributes:
<xs:attributeGroup name="ExtensionBaseAttributes">
<xs:attribute name="Executable" type="ST_Executable" use="optional"/>
<xs:attribute name="EntryPoint" type="ST_EntryPoint" use="optional"/>
<xs:attribute name="RuntimeType" type="ST_ActivatableClassId" use="optional"/>
<xs:attribute name="StartPage" type="ST_FileName" use="optional"/>
</xs:attributeGroup>
Because ServiceId allows the Extension base attributes, it has these semantic validations that aren't covered by the XSD manifest schema:
Extension base attributes must follow these rules:
- If the StartPage attribute is specified, fail if the EntryPoint, Executable, or RuntimeType attribute is specified.
- Otherwise, fail if the Executable or RuntimeType attribute is specified without an EntryPoint specified.
If ServiceId defines the EntryPoint attribute, either this ServiceId or the parent Extension or Application element must specify an Executable attribute.
Requirements
Value | |
---|---|
Namespace | http://schemas.microsoft.com/appx/2013/manifest |