Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

6 Appendix A: Product Behavior

This document specifies version-specific details in the Microsoft .NET Framework. The following versions of .NET Framework are available in the following released Windows product or as supplemental software, see .NET Framework.

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:

  • Microsoft .NET Framework 1.0

  • Microsoft .NET Framework 1.1

  • Microsoft .NET Framework 2.0

  • Microsoft .NET Framework 3.5

  • Microsoft .NET Framework 4.0

  • Microsoft .NET Framework 4.5

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 2.2.3.1: An ASP.NET web server uses the virtual path of the current application as an application identifier.

<2> Section 2.2.3.2: An ASP.NET web server obtains the application domain identifier from HttpRuntime.AppDomainAppIdInternal and then hashes the value by using the ASP.NET machine validation key. The result is then encoded by using base64. It is the base64-encoded representation that an ASP.NET web server uses as the application domain identifier of a web application.

<3> Section 2.2.3.3: ASP.NET web servers acting as session state clients use a specific value for this field.

<4> Section 2.2.3.4: A state server implementation must follow certain conventions for this field when it is used with an ASP.NET web server as the client.

<5> Section 3.1.3: The default Microsoft state server implementation requires that the state server is started and running prior to its use by a client.

<6> Section 3.1.5.1: The ASP.NET web server allows developers to specify whether web pages require exclusive or non-exclusive access to session state.

<7> Section 3.1.5.2: The ASP.NET web server allows developers to specify whether web pages require exclusive or non-exclusive access to session state.

<8> Section 3.2.1: ASP.NET stores a unique session identifier in an HTTP cookie that the browser passes back to an ASP.NET web server on each request.

<9> Section 3.2.3: The default Microsoft state server implementation requires that the state server is started and running prior to its use by a client.

<10> Section 3.2.3: The default Microsoft client implementation uses specific values for these fields, as described in Appendix A.

<11> Section 3.2.5.1: The ASP.NET web server allows developers to specify whether web pages require exclusive or non-exclusive access to session state.

<12> Section 3.2.5.1: The default Microsoft client retains these values and uses them to attempt to asynchronously unlock session state when the lock time has expired.

<13> Section 3.2.5.1: The default Microsoft client raises an exception if a bad request occurred.

<14> Section 3.2.5.2: The ASP.NET web server allows developers to specify whether web pages require exclusive or non-exclusive access to session state.

<15> Section 3.2.5.2: The default Microsoft client retains these values and uses them to attempt to asynchronously unlock session state when the lock time has expired.

<16> Section 3.2.5.2: The default Microsoft client raises an exception if a bad request occurred.

<17> Section 3.2.5.3: The default Microsoft client obtains this value from the configuration.

<18> Section 3.2.5.3: The default Microsoft client raises an exception if a bad request occurred.

<19> Section 3.2.5.4: The default Microsoft client raises an exception if a bad request occurred.

<20> Section 3.2.5.5: The default Microsoft client raises an exception if a bad request occurred.

<21> Section 3.2.5.6: The default Microsoft client raises an exception.

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.