ASP.NET

Software developer can disable session state management using option “Off”. This can provide a slight performance improvement for websites that are not using session state:

<?xml version=”1.0” encoding=”utf-8” ?>
<configuration>
     <system.web>
     <!— other settings are omitted. —>
     <sessionState
        cookieless=”AutoDetect” cookieName=”ASP.NET_SessionID”
        regenerateExpiredSessionID=”false”
        timeout=”20”
        mode=”Off”
        stateConnectionString=”tcpip=127.0.0.1:42424”
        stateNetworkTimeout=”10”
        sqlConnectionString=”data source=127.0.0.1;Integrated Security=SSPI”
        sqlCommandTimeout=”30” allowCustomSqlDatabase=”false”
        customProvider=””
     />
     </system.web>
</configuration>

Related TutorialsHow to consume a web service in ASP.NET
How to use the Menu navigation control in ASP.NET in VB.NET
How to use …

Learn more

Software developer can configure session state mode by default if he set it to “InProc”. In this case the other two settings have no effect. In this mode the information will be stored in the same process as the ASP.NET worker threads, i.e. software developer will expect best performance, but the least durability. If he restart web server, …

Learn more

Timeout is important session state setting in the web.config file. It specifies the number of minutes that ASP.NET will wait, without receiving a request, before it abandons the session.

<?xml version=”1.0” encoding=”utf-8” ?>
<configuration>
     <system.web>
     <!— other settings are omitted. —>
     <sessionState
        cookieless=”AutoDetect” cookieName=”ASP.NET_SessionID”
        regenerateExpiredSessionID=”false”
        timeout=”20”
        mode=”InProc”
        stateConnectionString=”tcpip=127.0.0.1:42424”
        stateNetworkTimeout=”10”
        sqlConnectionString=”data source=127.0.0.1;Integrated Security=SSPI”
        sqlCommandTimeout=”30” allowCustomSqlDatabase=”false”
        customProvider=””
     />
     </system.web>
</configuration>

This parameter is one of the most important, because a difference of minutes can have an impressive …

Learn more

Software developer can configure session state through web.config file for his current application (which is found in the same virtual directory as the .aspx web page files).  UseDeviceProfile is the one of possible modes for HttpCookieMode. When this mode is set ASP.NET attempts to determine whether the browser supports cookies by attempting to set and retrieve a cookie. …

Learn more

Software developer can configure session state through web.config file for his current application (which is found in the same virtual directory as the .aspx web page files).  UseDeviceProfile is the one of possible modes for HttpCookieMode. When this mode is set ASP.NET chooses to use cookieless sessions by examining the BrowserCapabilities object. The drawback is that this object …

Learn more

Software developer can configure session state through web.config file for his current application (which is found in the same virtual directory as the .aspx web page files). UseUri is the one of possible modes for HttpCookieMode. When this mode is set cookies will be never used, regardless of the capabilities of the browser or device. Instead, the …

Learn more

Software developer can configure session state through web.config file for his current application (which is found in the same virtual directory as the .aspx web page files).  UseCookies is the one of possible modes for HttpCookieMode. When this mode is set cookies will be always used, even if the browser or device do not support them or they …

Learn more