c:invoke-package

<c:invoke-package
  package = expression
  package-params? = expression(Object | IDictionary<String, Object>)
  initial-template? = { eqname }
  initial-mode? = { eqname }
  initial-match-selection? = expression
  template-params? = expression(Object | IDictionary<String, Object>)
  tunnel-params? = expression(Object | IDictionary<String, Object>)
  tunnel-passthru? = { boolean }
  base-output-uri? = { uri }
  base-uri? = { uri } />

Invokes a dynamically loaded package.

Category
instruction
Permitted parent elements
Any XCST element whose content model is sequence-constructor
Any literal result element

Attributes

base-output-uri The base output URI, used to resolve relative URIs of secondary result documents.
base-uri The base URI, used to resolve relative URIs.
initial-match-selection The value of the initial match selection.
initial-mode The name of the initial mode.
initial-template The name of the initial template.
package The package instance.
package-params An object with package parameters.
template-params An object with template parameters.
tunnel-params An object with tunnel parameters.
tunnel-passthru Specifies whether to pass the current tunnel parameters.

In addition to the attributes in the preceding table, there are a number of standard attributes that may appear on any XCST element.

Example: Displaying a Sign-in Form Without Redirecting

The following example uses the LoadPage method available in ASP.NET to dynamically load the sign-in page of a web app and call the content template.

<c:invoke-package package='LoadPage("/account/sign-in.xcst")'
   initial-template='content'
   tunnel-params='new { returnUrl = this.Request.Url.PathAndQuery }'/>