ApplicationHost.NotifyContextChange Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Overloads
NotifyContextChange(IHostedApplication) |
Notifies a single hosted application of the context change. |
NotifyContextChange(Boolean) |
Obsolete.
Notifies all the applications of the current context. |
NotifyContextChange() |
Notify all the applications of the current context. |
NotifyContextChange(IHostedApplication)
Notifies a single hosted application of the context change.
public:
void NotifyContextChange(Microsoft::Uii::Csr::IHostedApplication ^ app);
public void NotifyContextChange (Microsoft.Uii.Csr.IHostedApplication app);
member this.NotifyContextChange : Microsoft.Uii.Csr.IHostedApplication -> unit
Public Sub NotifyContextChange (app As IHostedApplication)
Parameters
Specifies the application to notify
Applies to
NotifyContextChange(Boolean)
Caution
This method has been deprecated, use NotifyContextChange() instead!
Notifies all the applications of the current context.
public:
virtual void NotifyContextChange(bool taggedApplicationsOnly);
[System.Obsolete("This method has been deprecated, use NotifyContextChange() instead!")]
public virtual void NotifyContextChange (bool taggedApplicationsOnly);
[<System.Obsolete("This method has been deprecated, use NotifyContextChange() instead!")>]
abstract member NotifyContextChange : bool -> unit
override this.NotifyContextChange : bool -> unit
Public Overridable Sub NotifyContextChange (taggedApplicationsOnly As Boolean)
Parameters
- taggedApplicationsOnly
- Boolean
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.
- Attributes
Applies to
NotifyContextChange()
Notify all the applications of the current context.
public:
virtual void NotifyContextChange();
public virtual void NotifyContextChange ();
abstract member NotifyContextChange : unit -> unit
override this.NotifyContextChange : unit -> unit
Public Overridable Sub NotifyContextChange ()