Поделиться через

ApplicationHost.NotifyContextChange Method (Boolean)

  • Статья

Notifies all the applications of the current context.

Namespace: Microsoft.Uii.Csr
Assembly: Microsoft.Uii.Csr.Core (in Microsoft.Uii.Csr.Core.dll)

Usage

'Usage
Dim instance As ApplicationHost
Dim taggedApplicationsOnly As Boolean

instance.NotifyContextChange(taggedApplicationsOnly)

Syntax

'Declaration
<ObsoleteAttribute("This method has been deprecated, use NotifyContextChange() instead!")> _
Public Overridable Sub NotifyContextChange ( _
    taggedApplicationsOnly As Boolean _
)

[ObsoleteAttribute("This method has been deprecated, use NotifyContextChange() instead!")] 
public virtual void NotifyContextChange (
    bool taggedApplicationsOnly
)

[ObsoleteAttribute(L"This method has been deprecated, use NotifyContextChange() instead!")] 
public:
virtual void NotifyContextChange (
    bool taggedApplicationsOnly
)

/** @attribute ObsoleteAttribute("This method has been deprecated, use NotifyContextChange() instead!") */ 
public void NotifyContextChange (
    boolean taggedApplicationsOnly
)

ObsoleteAttribute("This method has been deprecated, use NotifyContextChange() instead!") 
public function NotifyContextChange (
    taggedApplicationsOnly : boolean
)

Parameters

  • taggedApplicationsOnly
    True if only tagged global and tagged non-global applications should be updated with the latest context. This case occurs when a workflow had been just started. When a workflow is started, we freshly load the tagged non-global applications so they require the context. And we make the required tagged global applications visible so they should also receive the latest context. But as untagged apps have already received the context when the session is started, they need not be updated again. False - All global (untagged and tagged) apps and untagged non-global apps should be updated with the changed context. This case occurs in two situations. 1. When session is started. - At this point, the untagged global apps should get the context. As hostedApps contains only the untagged global apps now, instruction to inform all global apps will not have any effect on tagged global apps (tagged global apps will be active only when a workflow is started but not immediately after session is started and so they should not be informed about context change when session is started but they should be updated only when a workflow is started). 2. Session changed (switching between session) - At this point, all global apps should receive the changed context. Now hostedApps contains all types (all global and non-global). Among them only the global apps and untagged non-global should be updated with the context.

Thread Safety

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Platforms

See Also

Reference

ApplicationHost Class
ApplicationHost Members
Microsoft.Uii.Csr Namespace

Unified Service Desk
Send comments about this topic to Microsoft.
© 2015 Microsoft. All rights reserved.