• Choose a category
• All
• Classic-Fiction

sqlConnectionString

Used when the mode is set to SQLServer; specifies the connection string for the SQL Server database to use for storing session data.

stateConnectionString

Used when the mode is set to StateServer; specifies the server name and port where session state should be stored.

stateNetworkTimeout

Specifies the number of seconds the TCP/IP network connection between the Web server and the state server can be idle before the request is canceled. The default is 10.

timeout

Specifies the number of minutes a session can be idle before it is abandoned. The default is 20.

useHostingIdentity

Indicates that the ASP.NET process identity is impersonated to access a custom state provider or the SQLServer provider configured for integrated security. It’s true by default.

In addition, the child section lists custom session-state store providers. ASP.NET session state is designed to enable you to easily store user session data in different sources, such as a Web server’s memory or SQL Server. A store provider is a component that manages the storage of session-state information and stores it in alternative media (for example, an Oracle database) and with an alternative layout.

The default connection string for the SQLServer mode is set to the following:

data source=127.0.0.1;Integrated Security=SSPI

As you can see, it doesn’t contain the database name, which defaults to AspState. You create this database before the application is released using either T-SQL scripts or the aspnet_regsql command-line utility.

The default connection string for the StateServer mode is set to

tcpip=127.0.0.1:42424

You can change the TCP/IP address and the port used at will. Note, though, that to change the port you must edit the Port entry under the registry key:

HKEY_LOCAL_MACHINE\

SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters

In other words, just writing the new port number in the configuration file is not enough.

The Section

The section configures settings and providers for the ASP.NET site navigation system. The schema of the section is quite simple:

enabled="true|false"

defaultProvider="provider name">

...

The feature relies on site-map providers—that is, made-to-measure components that return information representing the structure of the site. ASP.NET comes with one predefined provider: the AspNetXmlSiteMapProvider class. The default site-map provider is specified through the defaultProvider attribute. All available providers, including custom providers, are listed in the section.

The Section

Tracing refers to the program’s ability to send informative messages about the status of the execution. In general, tracing is a way to monitor the behavior of an application in a production environment, and debugging is used for development time testing. The section defines attributes that can modify the behavior of application-level tracing. The attributes are listed in Table 3-15.

Table 3-15. Application-Level ASP.NET Tracing Attributes

Attribute

Description

enabled

Specifies whether tracing is enabled for an application. The default is false. Tracing must be enabled in order to use the trace viewer (trace.axd) and other tracing facilities.

localOnly

If this attribute is set to true, the trace viewer is available only on the local host; if it’s set to false, the trace viewer is also available remotely. The default is true. Note that trace.axd is one of the default HTTP handlers registered at installation time.

pageOutput

Specifies whether trace output is rendered at the end of each page. If this attribute is set to false, trace output is accessible through the trace viewer only. The default is false. Regardless of this global setting, individual pages can enable tracing using the Trace attribute of the @Page directive.

requestLimit

Indicates the maximum number of trace results to store on the server that are subsequently