System.Web
2.0.0.0
System.Configuration.ConfigurationSection
The class provides a way to programmatically access and modify the content of the configuration file pages section. This configuration section supports setting certain ASP.NET page and control directives globally for all pages and controls in the scope of the configuration file. This includes the @ Page directive, the @ Import directive through the collection property, and the @ Register directive through the collection property. It also provides support for mapping tag types to other tag types at run time through the collection property.
Directives specify settings used by the page and user-control compilers when they process ASP.NET Web Forms page (.aspx) and user control (.ascx) files.
Provides programmatic access to the pages section of the configuration file. This class cannot be inherited.
Constructor
The constructor is not intended to be used directly from your code. It is called by the ASP.NET configuration system. You obtain an instance of the class by using the method.
Initializes a new instance of the class using default settings.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("asyncTimeout", DefaultValue="00:00:45")
System.ComponentModel.TypeConverter(typeof(System.Configuration.TimeSpanSecondsConverter))
System.Configuration.TimeSpanValidator(MinValueString="00:00:00", MaxValueString="10675199.02:48:05.4775807")
System.TimeSpan
To be added.
The default value is 45 seconds.
Gets or sets a value indicating the number of seconds to wait for an asynchronous handler to complete during asynchronous page processing.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("autoEventWireup", DefaultValue=true)
System.Boolean
To be added.
When is true, ASP.NET does not require that you explicitly bind event handlers to a page event such as .
When is false, you must explicitly bind the event to a method. For example, if you have a Page_Load method in the code for a page, the method will be called in response to the event only if you write code like that in the following example (notice the Handles statement in Visual Basic and the event handler code in C#):
Partial Class AutoEventWireupExample
Inherits System.Web.UI.Page
Protected Sub Page_Load(ByVal sender As Object, _
ByVal e As System.EventArgs) Handles Me.Load
Response.Write("Executing Page_Load")
End Sub
End Class
public partial class AutoEventWireupExample : System.Web.UI.Page
{
protected void Page_Load(object sender, System.EventArgs e)
{
Response.Write("Executing Page_Load");
}
override protected void OnInit(EventArgs e)
{
this.Load += new System.EventHandler(this.Page_Load);
}
}
When is true, handlers are automatically bound to events at run time based on their name and signature. For each event, ASP.NET searches for a method that is named according to the pattern Page_eventname, such as Page_Load or Page_Init. ASP.NET checks first for an overload that has the typical event-handler signature (that is, it specifies and parameters). If an event handler with this signature is not found, ASP.NET checks for an overload that has no parameters.
When is false, you must explicitly bind event handlers to events, as shown in the preceding example. In that case, the method names do not have to follow a pattern.
The default value is true if is not specified in the @ Page directive. Visual Studio automatically includes the attribute when it creates code-behind files. For ASP.NET pages written in C#, Visual Studio sets the value to true. For Visual Basic, Visual Studio sets the value to false because handlers are bound to events by using the Handles keyword, which is inserted automatically by Visual Studio when it generates an event handler. If you set to true, you can omit (or remove) the Handles keyword.
Do not set to true if performance is a key consideration. When automatic event wireup is enabled, ASP.NET must make between 15 and 30 tries to match events with methods.
Note the following about binding event handlers to events:
-
If you set to true, make sure that you do not also manually attach page event handlers to events. If you do, handlers might be called more than one time.
-
Automatic binding is performed only for page events, not for events for controls on the page.
-
As an alternative to binding events to handlers, you can override the Oneventname methods of the page or of controls.
Gets or sets a value indicating whether events for ASP.NET pages are automatically connected to event-handling functions.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("buffer", DefaultValue=true)
System.Boolean
To be added.
When response buffering is turned on, the page or control output is buffered until after the entire page or control is processed. Do not set to true if performance is a key consideration.
Gets or sets a value that specifies whether .aspx pages and .ascx controls use response buffering.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("compilationMode", DefaultValue=System.Web.UI.CompilationMode.Always)
System.Web.UI.CompilationMode
To be added.
The default value is .
Gets or sets a value that determines how .aspx pages and .ascx controls are compiled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("controls")
System.Web.Configuration.TagPrefixCollection
To be added.
The objects correspond to the @ Register directive on an ASP.NET page. The @ Register directive allows you to specify the tag prefix for a user control.
Gets a collection of objects.
2.0.0.0
Method
System.Void
To be added.
To be added.
To be added.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enableEventValidation", DefaultValue=true)
System.Boolean
To be added.
The attribute indicates whether event validation should be performed. The default value is true. A Web application can optionally disable event validation to revert to .NET Framework version 1.0 behavior.
The base control checks this attribute to determine whether it should validate events. A derived control does not inherit this base control attribute, and so it is exempt from event validation by default. You still instruct ASP.NET to perform event validation on the derived control by adding the attribute to the derived control itself and setting it to true.
Event validation reduces the risk of unauthorized postback requests and callbacks. It instructs ASP.NET to validate only those events that can be raised in the control during a postback request or callback. With this model, a control registers its events during rendering and then validates the events during the post-back or callback handling. All event-driven controls in ASP.NET use this feature by default.
Gets or sets a value that specifies whether event validation is enabled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enableSessionState", DefaultValue="true")
System.Web.Configuration.PagesEnableSessionState
To be added.
To be added.
Gets or sets a value that specifies whether the session state is enabled, disabled, or read-only.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enableViewState", DefaultValue=true)
System.Boolean
To be added.
To be added.
Gets or sets a value indicating whether view state is enabled or disabled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enableViewStateMac", DefaultValue=true)
System.Boolean
To be added.
A view-state MAC is an encrypted version of the hidden variable that a page's view state is persisted to when the page is sent to the browser. When this property is set to true, the encrypted view state is checked to verify that it has not been tampered with on the client.
This attribute should never be set to false in a production Web site.
Gets or sets a value that specifies whether ASP.NET should run a message authentication code (MAC) on the page's view state when the page is posted back from the client.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("maintainScrollPositionOnPostBack", DefaultValue=false)
System.Boolean
To be added.
To be added.
Gets or sets a value indicating whether the page scroll position should be maintained upon returning from a postback from the server.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("masterPageFile", DefaultValue="")
System.String
To be added.
The value of this property can be either a relative or an absolute path.
Gets or sets a reference to the master page for the application.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("maxPageStateFieldLength", DefaultValue=-1)
System.Int32
To be added.
Page and control view state is stored in hidden view-state fields when the page or control is rendered. If the length of the data stored exceeds the value, then the data is split between multiple view-state fields.
Gets or sets the maximum number of characters that a single view-state field can contain.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("namespaces")
System.Web.Configuration.NamespaceCollection
To be added.
The objects correspond to the @ Import directive on an ASP.NET page. The Import directive allows you to specify namespaces that are automatically imported into all the pages of an application.
Gets a collection of objects.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("pageBaseType", DefaultValue="System.Web.UI.Page")
System.String
To be added.
To be added.
Gets or sets a value that specifies a code-behind class that .aspx pages inherit by default.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("pageParserFilterType", DefaultValue="")
System.String
To be added.
A parser filter, which is an instance of the class, is called by the page compilation process before the parsing step to allow for changes to the source code at run time.
Gets or sets a value that specifies the parser filter type.
2.0.0.0
Property
System.Configuration.ConfigurationPropertyCollection
To be added.
To be added.
To be added.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("smartNavigation", DefaultValue=false)
System.Boolean
To be added.
Smart navigation requires Microsoft Internet Explorer 5.5 or greater.
Gets or sets a value that indicates whether smart navigation is enabled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("styleSheetTheme", DefaultValue="")
System.String
To be added.
To be added.
Gets or sets the name of an ASP.NET style sheet theme.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("tagMapping")
System.Web.Configuration.TagMapCollection
To be added.
The object has no corresponding directive on an ASP.NET page. The objects allow you to remap tag type names to other type names at compile time.
Gets a collection of objects.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("theme", DefaultValue="")
System.String
To be added.
To be added.
Gets or sets the name of an ASP.NET page theme.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("userControlBaseType", DefaultValue="System.Web.UI.UserControl")
System.String
To be added.
To be added.
Gets or sets a value that specifies a code-behind class that user controls inherit by default.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("validateRequest", DefaultValue=true)
System.Boolean
To be added.
Request validation is performed by comparing all input data to a list of potentially dangerous values. If a match occurs, ASP.NET raises an .
Gets or sets a value that determines whether ASP.NET examines input from the browser for dangerous values. For more information, see Script Exploits Overview.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("viewStateEncryptionMode", DefaultValue=System.Web.UI.ViewStateEncryptionMode.Auto)
System.Web.UI.ViewStateEncryptionMode
To be added.
The possible enumeration values are Always, Auto, and Never. The default value is Auto. If property is set to Auto, ViewState will be encrypted when a control requests it.
Gets or sets the encryption mode that ASP.NET uses when maintaining ViewState values.
2.0.0.0