HttpRuntimeSection.MaxWaitChangeNotification Property

Reference

Definition

Namespace:: System.Web.Configuration

Assembly:: System.Web.dll

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.

Gets or sets the time interval between the first change notification and the time at which the application ___domain is restarted.

public:
 property int MaxWaitChangeNotification { int get(); void set(int value); };

[System.Configuration.ConfigurationProperty("maxWaitChangeNotification", DefaultValue=0)]
[System.Configuration.IntegerValidator(MinValue=0)]
public int MaxWaitChangeNotification { get; set; }

[<System.Configuration.ConfigurationProperty("maxWaitChangeNotification", DefaultValue=0)>]
[<System.Configuration.IntegerValidator(MinValue=0)>]
member this.MaxWaitChangeNotification : int with get, set

Public Property MaxWaitChangeNotification As Integer

Property Value

Int32

The maximum time interval, in seconds, from the first change notification and the time when the application ___domain is restarted.

Attributes: ConfigurationPropertyAttribute IntegerValidatorAttribute

Examples

The following example shows how to use the MaxWaitChangeNotification property.

// Get the current MaxWaitChangeNotification property value.
Response.Write("MaxWaitChangeNotification: " +
  configSection.MaxWaitChangeNotification + "<br>");

// Set the MaxWaitChangeNotification property value to 10 seconds.
configSection.MaxWaitChangeNotification = 10;

' Get the current MaxWaitChangeNotification property value.
Response.Write("MaxWaitChangeNotification: " & _
  configSection.MaxWaitChangeNotification & "<br>")

' Set the MaxWaitChangeNotification property value to 10 seconds.
configSection.MaxWaitChangeNotification = 10

Remarks

A suggested value for the MaxWaitChangeNotification property would exceed the length of time to complete a copy during the deployment process.

Note

The content might appear cached if you view it immediately after a copy-and-deploy process. This is typical behavior. The changes take effect when the wait period that you specified has elapsed.

Applies to

Share via