Windows Dev Center

LaunchAction (in AppointmentsProviderLaunchActions)

Applies to Windows and Windows Phone

Describes an AppointmentsProviderLaunchActions content action.

Element hierarchy

<Extension>
<AppointmentsProvider>
<AppointmentsProviderLaunchActions>
<LaunchAction>

Syntax

<LaunchAction Verb         = "addAppointment" | "removeAppointment" | "replaceAppointment" | "showTimeFrame"
              DesiredView? = "default" | "useLess" | "useHalf" | "useMore" | "useMinimum" />

Key

?   optional (zero or one)

Attributes and Elements

Attributes

AttributeDescriptionData typeRequiredDefault value
DesiredView

The desired amount of screen space to use when the appointment launches.

Windows Phone:  DesiredView isn't supported for Windows Phone.

This attribute can have one of the following values:

  • default
  • useLess
  • useHalf
  • useMore
  • useMinimum
No
Verb

A unique identifier that is passed to the app when it is launched. The app can use this string to determine which AppointmentsProviderLaunchActions handler triggered its launch. It is unique per application in the package and is case sensitive.

This attribute can have one of the following values:

  • addAppointment
  • removeAppointment
  • replaceAppointment
  • showTimeFrame
Yes

 

Child Elements

None.

Parent Elements

Parent ElementDescription
AppointmentsProviderLaunchActions

Declares actions to take when a appointment is launched.

 

Related elements

The following elements have the same name as this one, but different content or attributes:

Remarks

For more info about launch actions that an appointments provider takes, see AppointmentsProviderLaunchActionVerbs.

The LaunchAction (in AppointmentsProviderLaunchActions) definition has these statements:


            <xs:element name="LaunchAction" minOccurs="0" maxOccurs="10">
              <xs:complexType>
                <xs:attribute name="Verb" type="ST_AppointmentsProviderLaunchActionVerbs" use="required"/>
                <xs:attribute name="DesiredView" type="ST_DesiredView" use="optional"/>
                <xs:attributeGroup ref="m:ExtensionBaseAttributes"/>
              </xs:complexType>
            </xs:element>

The preceding 'ref' statement indicates that LaunchAction (in AppointmentsProviderLaunchActions) inherits and 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 LaunchAction (in AppointmentsProviderLaunchActions) 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 LaunchAction defines the EntryPoint attribute, either this LaunchAction or the parent Extension or Application element must specify an Executable attribute.

Requirements

Namespace

http://schemas.microsoft.com/appx/2013/manifest

 

 

Show:
© 2015 Microsoft