REGISTER  |  SIGN IN
United States Patent7117504
Smith , ; et al.October 3, 2006
Title
Application program interface that enables communication for a network software platform
Abstract
An application program interface includes a first class to provide information regarding a current HTTP request. The application program interface also includes a second class to manage HTTP output to a client and an object to provide access to server-side utilities and processes. Particular application program interfaces include additional classes to manipulate cookies, handle file transfers, provide exception information, or control operation of an output cache.
Inventors:Smith; Adam W. (Redmond, WA), Moore; Anthony J.  (Seattle, WA), Ebbo; David S.  (Redmond, WA), Christensen; Erik B.  (Seattle, WA), Olson; Erik B.  (Sammamish, WA), Yeon; Fabio A.  (Mill Creek, WA), Rajan; Jayanth V.  (Bellevue, WA), Ballinger; Keith W.  (North Bend, WA), Vasandani; Manu  (Bellevue, WA), Anders; Mark T.  (Bellevue, WA), Boulter; Mark A.  (Redmond, WA), Kothari; Nikhil  (Sammamish, WA), Howard; Robert M.  (Snoqualmie, WA), Guthrie; Scott D.  (Bellevue, WA), Millet; Stephen J.  (Edmonds, WA), Pharies; Stefan H.  (Seattle, WA), Cook; Suzanne M.  (Redmond, WA), Warren; Susan M.  (Carnation, WA), Christensen; Yann E.  (Seattle, WA)
Assignee:Microsoft Corporation (Redmond, WA)
Appl. No.:09/902,809
Filed:July 10, 2001
Current U.S. Class:719/328 709/201 709/227 
Current International Class:G06F 9/00 (20060101)
Field of Search:709/328,217-219,200-203,230-232 719/328,310-319,329-332 715/513 717/114
U.S. Patent Documents
20020073236June 2002Helgeson
20020099687July 2002Krishnaprasad et al.
20020169679November 2002Neumayer
20030028685February 2003Smith et al.
20030051236March 2003Pace et al.
20030074206April 2003Hoffman et al.
20030084120May 2003Egli
20030120665June 2003Fox et al.
20030167277September 2003Hejlsberg et al.
20030167355September 2003Smith et al.
20030167356September 2003Smith et al.
20030172196September 2003Hejlsberg et al.
20030177282September 2003Hejlsberg et al.
20040117759June 2004Rippert, Jr.
5218699June 1993Brandle et al.
5430876July 1995Schreiber et al.
5689700November 1997Miller et al.
5748962May 1998Brechtel et al.
5761494June 1998Smedley et al.
5822580October 1998Leung
5903753May 1999Bramnick et al.
5937406August 1999Balabine et al.
5956509September 1999Kevner
5987517November 1999Firth et al.
6061743May 2000Thatcher et al.
6175878January 2001Seaman et al.
6209124March 2001Vermeire et al.
6256678July 2001Traughber et al.
6275871August 2001Reinfelder et al.
6282581August 2001Moore et al.
6298354October 2001Saulpaugh et al.
6349343February 2002Foody et al.
6353830March 2002Yee et al.
6360230March 2002Chan et al.
6360266March 2002Pettus
6418448July 2002Sarkar
6430593August 2002Lindsley
6442548August 2002Balabine et al.
6446253September 2002Mellmer
6473794October 2002Guheen et al.
6519571February 2003Guheen et al.
6536037March 2003Guheen et al.
6615166September 2003Guheen et al.
6643652November 2003Helgeson et al.
6721713April 2004Guheen et al.
6792605September 2004Roberts et al.
Other References
Deitel et al. Java How to Program book, Prentice Hall, Third edition, 1999 (pp. 7-29, 698-699, 714-717, 876-878, 936-977, 980-998, 1002-1046). cited by examiner .
Deitel et al. Java How to Program book, Prentice Hall, Third edition, 1999 (additional cited pages, 214-226, 817-838) Note: other pages refer to previously provided form PTO-892, paper No. 6, dated Feb. 2, 2004. cited by examiner .
Tim O'Reilly, The Network Really Is the Computer, The O'Reilly Network at (http://www.oreilyynet.com) Jun. 8, 2000, pp. 1-11. cited by other .
The Java tm 2 Enterprise Developer's Guide, v1.2.1, May 2000, Sun Microsystems, Palo Alto Ca. U.S.A., chapter 1; pp. 1-10 & pp. 152-155. cited by other .
Bill Shannon, Java tm 2 Platform Enterprise Edition Specification , v1.2, Sun Microsystems, Palo Alto Ca. U.S.A., Dec. 17, 1999, pp. 2-1 thru 2-7 & 6-1. cited by other .
Java tm 2 Platform, Standard Edition, v1.2.2 API Specification, 1993-1999 Sun Microsystems, Inc. in the U.S.A. and other countries. Palo Alto Ca. U.S.A, pp.1-4. cited by other .
Lam et al.; NET Framework Essentials Jun. 2001 O'Reilly pp. 1-32. cited by other .
NET is coming [Microsoft Web Services platform] IEEE Computer vol.: 34 Issue: Aug. 8, 2001 pp. 92-97. cited by other .
Cheng et al.; "XML and DB2" IEEE Data Engineering 2000. Proceedings 16 International Conference on Feb. 29-Mar. 3, 2000 pp. 569-573. cited by other .
Shannon; "Java 2 Platrform Enterprise Edition Specification" v1.2 Dec. 17, 1999 pp. 2-8 thru 2-11 and 6-2 thru 6-6. cited by other .
Flanagan; "Java in a Nutshell" O'Reilly & Associates 1996 pp. 193-200; 237-253 267-270 339-342. cited by other .
U.S. Appl. No. 10/087,027, filed Feb. 28, 2002, entitled "Application Program Interface for Network Software Platform.". cited by other .
U.S. Appl. No. 09/902,811, filed Jul. 10, 2001, entitled "Application Program Interface for Network Software Platform.". cited by other .
U.S. Appl. No. 09/902,560, filed Jul. 10, 2001, entitled "Application Program Interface for Network Software Platform.". cited by other .
U.S. Appl. No. 09/902,810, filed Jul. 10, 2001, entitled "Application Program Interface for Network Software Platform.". cited by other .
U.S. Appl. No. 09/902,812, filed Jul. 10, 2001, entitled "Application Program Interface for Network Software Platform.". cited by other .
U.S. Appl. No. 09/901,555, filed Jul. 10, 2001, entitled "Application Program Interface for Network Software Platform.". cited by other .
H. Carr, et al, "Compiling Distributed C++", IEEE, 1993, pp. 496-503. cite- d by other .
Deitel & Deitel "Java(TM) How to Program book" Prentice Hall Third edition 1999 (pp. 7-29, 214-226, 698-699, 714-717, 817-838, 876-878, 936-977, 980-998, 1002-1046). cited by other .
Arulanthu, et al, "The Design and Performanceof A Scalable ORB Architecture for COBRA Asynchronous Messaging." Middleware 2000, Springer-Verlag, 2000,pp. 208-228. cited by other .
Hanson, "Differences between J2SE and J2EE", Sep. 8, 2003, SearchTechTarget.com. cited by other.~
Primary Examiner: Follansbee; John
Assistant Examiner: Patel; Haresh
Attorney, Agent or Firm:Lee & Hayes, PLLC
Claims

The invention claimed is:
1. A computer system including one or more microprocessors and one or more software programs, the one or more software programs utilizing an application program interface to request services from an operating system, the application program interface including separate commands to request services consisting of the following groups of services: a first group of services related to information regarding a current HTTP request; a second group of services related to managing HTTP output to a client, wherein the second group of services is further related to obtaining information regarding capabilities of a web browser running on the client; a third group of services related to providing access to server-based utilities; a fourth group of services related to creating web services; a fifth group of services related to sharing global information across multiple sessions associated with an application; a sixth group of services related to caching frequently used resources; and a seventh group of services related to obtaining information regarding a platform type associated with the client.
Description


RELATED APPLICATIONS

This application is related to the following applications:

Ser. No. 10/087,027, filed Feb. 28, 2002, which is a Continuation of Ser. No. 09/902,936, filed Jul. 10, 2001;

Ser. No. 09/901,555, filed Jul. 10, 2001;

Ser. No. 09/902,560, filed Jul. 10, 2001;

Ser. No. 09/902,810, filed Jul. 10, 2001;

Ser. No. 09/902,811, filed Jul. 10, 2001; and

Ser. No. 09/902,812, filed Jul. 10, 2001.

TECHNICAL FIELD

This invention relates to network software, such as Web applications, and to computer software development of such network software. More particularly, this invention relates to an application program interface (API) that facilitates use of a network software platform by application programs and computer hardware.

BACKGROUND

Very early on, computer software came to be categorized as "operating system" software or "application" software. Broadly speaking, an application is software meant to perform a specific task for the computer user such as solving a mathematical equation or supporting word processing. The operating system is the software that manages and controls the computer hardware. The goal of the operating system is to make the computer resources available to the application programmer while at the same time, hiding the complexity necessary to actually control the hardware.

The operating system makes the resources available via functions that are collectively known as the Application Program Interface or API. The term API is also used in reference to a single one of these functions. The functions are often grouped in terms of what resource or service they provide to the application programmer. Application software requests resources by calling individual API functions. API functions also serve as the means by which messages and information provided by the operating system are relayed back to the application software.

In addition to changes in hardware, another factor driving the evolution of operating system software has been the desire to simplify and speed application software development. Application software development can be a daunting task, sometimes requiring years of developer time to create a sophisticated program with millions of lines of code. For a popular operating system such as Microsoft Windows.RTM., application software developers write thousands of different applications each year that utilize the operating system. A coherent and usable operating system base is required to support so many diverse application developers.

Often, development of application software can be made simpler by making the operating system more complex. That is, if a function may be useful to several different application programs, it may be better to write it once for inclusion in the operating system, than requiring dozens of software developers to write it dozens of times for inclusion in dozens of different applications. In this manner, if the operating system supports a wide range of common functionality required by a number of applications, significant savings in applications software development costs and time can be achieved.

Regardless of where the line between operating system and application software is drawn, it is clear that for a useful operating system, the API between the operating system and the computer hardware and application software is as important as efficient internal operation of the operating system itself.

Over the past few years, the universal adoption of the Internet, and networking technology in general, has changed the landscape for computer software developers. Traditionally, software developers focused on single-site software applications for standalone desktop computers, or LAN-based computers that were connected to a limited number of other computers via a local area network (LAN). Such software applications were typically referred to as "shrink wrapped" products because the software was marketed and sold in a shrink-wrapped package. The applications utilized well-defined APIs to access the underlying operating system of the computer.

As the Internet evolved and gained widespread acceptance, the industry began to recognize the power of hosting applications at various sites on the World Wide Web (or simply the "Web"). In the networked world, clients from anywhere could submit requests to server-based applications hosted at diverse locations and receive responses back in fractions of a second. These Web applications, however, were typically developed using the same operating system platform that was originally developed for standalone computing machines or locally networked computers. Unfortunately, in some instances, these applications do not adequately transfer to the distributed computing regime. The underlying platform was simply not constructed with the idea of supporting limitless numbers of interconnected computers.

To accommodate the shift to the distributed computing environment being ushered in by the Internet, Microsoft Corporation is developing a network software platform known as the ".NET" platform (read as "Dot Net"). The platform allows developers to create Web services that will execute over the Internet. Such a dynamic shift requires a new ground-up design of an entirely new API.

In response to this challenge, the inventors developed a unique set of API functions for Microsoft's .NET.TM. platform.

SUMMARY

An application program interface (API) provides a set of functions for application developers who build Web applications on a network platform, such as Microsoft Corporation's .NET.TM. platform.

BRIEF DESCRIPTION OF THE DRAWINGS The same numbers are used throughout the drawings to reference like features. FIG. 1 illustrates a network architecture in which clients access Web services over the Internet using conventional protocols. FIG. 2 is a block diagram of a software architecture for Microsoft's .NET.TM. platform, which includes an application program interface (API). FIG. 3 is a block diagram of unique namespaces supported by the API, as well as function classes of the various API functions. FIG. 4 is a block diagram of an exemplary computer that may execute all or part of the software architecture.

BRIEF DESCRIPTION OF ACCOMPANYING COMPACT DISC Accompanying this specification is a compact disc that stores a compiled HTML help file identifying the API (application program interface) for Microsoft's .NET.TM. network platform. The file is named "cpref.chm" and was created on Jun. 8, 2001. It is 30.81 Mbytes in size. The file can be executed on a Windows.RTM.-based computing device (e.g., IBM-PC, or equivalent) that executes a Windows.RTM.-brand operating system (e.g., Windows.RTM. NT, Windows.RTM. 98, Windows.RTM. 2000, etc.). The compiled HTML help file stored on the compact disk is hereby incorporated by reference. Additionally, the APIs contained in the compiled HTML help file are also provided in approximately 100 separate text files named "NamespaceName.txt". The text files comply with the ASCII format. The compact disc itself is a CD-ROM, and conforms to the ISO 9660 standard.

DETAILED DESCRIPTION This disclosure addresses an application program interface (API) for a network platform upon which developers can build Web applications and services. More particularly, an exemplary API is described for the .NET.TM. platform created by Microsoft Corporation. The .NET.TM. platform is a software platform for Web services and Web applications implemented in the distributed computing environment. It represents the next generation of Internet computing, using open communication standards to communicate among loosely coupled Web services that are collaborating to perform a particular task. In the described implementation, the .NET.TM. platform utilizes XML (extensible markup language), an open standard for describing data. XML is managed by the World Wide Web Consortium (W3C). XML is used for defining data elements on a Web page and business-to-business documents. XML uses a similar tag structure as HTML; however, whereas HTML defines how elements are displayed, XML defines what those elements contain. HTML uses predefined tags, but XML allows tags to be defined by the developer of the page. Thus, virtually any data items can be identified, allowing Web pages to function like database records. Through the use of XML and other open protocols, such as Simple Object Access Protocol (SOAP), the .NET.TM. platform allows integration of a wide range of services that can be tailored to the needs of the user. Although the embodiments described herein are described in conjunction with XML and other open standards, such are not required for the operation of the claimed invention. Other equally viable technologies will suffice to implement the inventions described herein. As used herein, the phrase application program interface or API includes traditional interfaces that employ method or function calls, as well as remote calls (e.g., a proxy, stub relationship) and SOAP/XML invocations. Exemplary Network Environment FIG. 1 shows a network environment 100 in which a network platform, such as the .NET.TM. platform, may be implemented. The network environment 100 includes representative Web services 102(1), . . . , 102(N), which provide services that can be accessed over a network 104
(e.g., Internet). The Web services, referenced generally as number 102, are programmable application components that are reusable and interact programmatically over the network 104, typically through industry standard Web protocols, such as XML, SOAP, WAP (wireless application protocol), HTTP (hypertext transport protocol), and SMTP (simple mail transfer protocol) although other means of interacting with the Web services over the network may also be used, such as Remote Procedure Call (RPC) or object broker type technology. A Web service can be self-describing and is often defined in terms of formats and ordering of messages. Web services 102 are accessible directly by other services (as represented by communication link 106) or a software application, such as Web application (as represented by communication links 112 and 114). Each Web service 102 is illustrated as including one or more servers that execute software to handle requests for particular services. Such services often maintain databases that store information to be served back to requesters. Web services may be configured to perform any one of a variety of different services. Examples of Web services include login verification, notification, database storage, stock quoting, location directories, mapping, music, electronic wallet, calendar/scheduler, telephone listings, news and information, games, ticketing, and so on. The Web services can be combined with each other and with other applications to build intelligent interactive experiences. The network environment 100 also includes representative client devices 120(1), 120(2), 120(3), 120(4), . . . , 120(M) that utilize the Web services 102 (as represented by communication link 122) and/or the Web application 110 (as represented by communication links 124, 126, and 128). The clients may communicate with one another using standard protocols as well, as represented by an exemplary XML link 130 between clients 120(3) and 120(4). The client devices, referenced generally as number 120, can be implemented many different ways. Examples of possible client implementations include, without limitation, portable computers, stationary computers, tablet PCs, televisions/set-top boxes, wireless communication devices, personal digital assistants, gaming consoles, printers, photocopiers, and other smart devices. The Web application 110 is an application designed to run on the network platform and may utilize the Web services 102 when handling and servicing requests from clients 120. The Web application 110 is composed of one or more software applications 130 that run atop a programming framework 132, which are executing on one or more servers 134 or other computer systems. Note that a portion of Web application 110 may actually reside on one or more of clients 120. Alternatively, Web application 110 may coordinate with other software on clients 120 to actually accomplish its tasks. The programming framework 132 is the structure that supports the applications and services developed by application developers. It permits multi-language development and seamless integration by supporting multiple languages. It supports open protocols, such as SOAP, and encapsulates the underlying operating system and object model services. The framework provides a robust and secure execution environment for the multiple programming languages and offers secure, integrated class libraries. The framework 132 is a multi-tiered architecture that includes an application program interface (API) layer 142, a common language runtime (CLR) layer 144, and an operating system/services layer 146. This layered architecture allows updates and modifications to various layers without impacting other portions of the framework. A common language specification (CLS) 140 allows designers of various languages to write code that is able to access underlying library functionality. The specification 140 functions as a contract between language designers and library designers that can be used to promote language interoperability. By adhering to the CLS, libraries written in one language can be directly accessible to code modules written in other languages to achieve seamless integration between code modules written in one language and code modules written in another language. One exemplary detailed implementation of a CLS is described in an ECMA standard created by participants in ECMA TC39/TG3. The reader is directed to the ECMA web site at www.ecma.ch. The API layer 142 presents groups of functions that the applications 130 can call to access the resources and services provided by layer 146. By exposing the API functions for a network platform, application developers can create Web applications for distributed computing systems that make full use of the network resources and other Web services, without needing to understand the complex interworkings of how those network resources actually operate or are made available. Moreover, the Web applications can be written in any number of programming languages, and translated into an intermediate language supported by the common language runtime 144 and included as part of the common language specification 140. In this way, the API layer 142
can provide methods for a wide and diverse variety of applications. Additionally, the framework 132 can be configured to support API calls placed by remote applications executing remotely from the servers 134 that host the framework. Representative applications 148(1) and 148(2) residing on clients 120(3) and 120(M), respectively, can use the API functions by making calls directly, or indirectly, to the API layer 142 over the network 104. The framework may also be implemented at the clients. Client 120(3) represents the situation where a framework 150 is implemented at the client. This framework may be identical to server-based framework 132, or modified for client purposes. Alternatively, the client-based framework may be condensed in the event that the client is a limited or dedicated function device, such as a cellular phone, personal digital assistant, handheld computer, or other communication/computing device. Developers' Programming Framework FIG. 2 shows the programming framework
132 in more detail. The common language specification (CLS) layer 140 supports applications written in a variety of languages 130(1), 130(2), 130(3), 130(4), . . . 130(K). Such application languages include Visual Basic, C++, C#, COBOL, Jscript, Perl, Eiffel, Python, and so on. The common language specification 140 specifies a subset of features or rules about features that, if followed, allow the various languages to communicate. For example, some languages do not support a given type (e.g., an "int*" type) that might otherwise be supported by the common language runtime 144. In this case, the common language specification 140 does not include the type. On the other hand, types that are supported by all or most languages (e.g., the "int[ ]" type) is included in common language specification 140 so library developers are free to use it and are assured that the languages can handle it. This ability to communicate results in seamless integration between code modules written in one language and code modules written in another language. Since different languages are particularly well suited to particular tasks, the seamless integration between languages allows a developer to select a particular language for a particular code module with the ability to use that code module with modules written in different languages. The common language runtime 144 allow seamless multi-language development, with cross language inheritance, and provide a robust and secure execution environment for the multiple programming languages. For more information on the common language specification 140 and the common language runtime 144, the reader is directed to co-pending applications entitled "Method and System for Compiling Multiple Languages", filed Jun. 21, 2000 (Ser. No. 09/598,105 now Pat. No. 6,836,883) and "Unified Data Type System and Method" filed Jul. 10, 2000 (Ser. No. 09/613,289 now abandoned), which are incorporated by reference. The framework 132 encapsulates the operating system
146(1) (e.g., Windows.RTM.-brand operating systems) and object model services 146(2) (e.g., Component Object Model (COM) or Distributed COM). The operating system 146(1) provides conventional functions, such as file management, notification, event handling, user interfaces (e.g., windowing, menus, dialogs, etc.), security, authentication, verification, processes and threads, memory management, and so on. The object model services 146(2) provide interfacing with other objects to perform various tasks. Calls made to the API layer 142 are handed to the common language runtime layer 144 for local execution by the operating system 146(1) and/or object model services 146(2). The API 142 groups API functions into multiple namespaces. Namespaces essentially define a collection of classes, interfaces, delegates, enumerations, and structures, which are collectively called "types", that provide a specific set of related functionality. A class represents managed heap allocated data that has reference assignment semantics. A delegate is an object oriented function pointer. An enumeration is a special kind of value type that represents named constants. A structure represents static allocated data that has value assignment semantics. An interface defines a contract that other types can implement. By using namespaces, a designer can organize a set of types into a hierarchical namespace. The designer is able to create multiple groups from the set of types, with each group containing at least one type that exposes logically related functionality. In the exemplary implementation, the API 142 is organized into four root namespaces: a first namespace 200 for Web applications, a second namespace 202 for client applications, a third namespace 204 for data and XML, and a fourth namespace 206 for base class libraries (BCLs). Each group can then be assigned a name. For instance, types in the Web applications namespace 200 are assigned the name "Web", and types in the data and XML namespace 204 can be assigned names "Data" and "XML" respectively. The named groups can be organized under a single "global root" namespace for system level APIs, such as an overall System namespace. By selecting and prefixing a top level identifier, the types in each group can be easily referenced by a hierarchical name that includes the selected top level identifier prefixed to the name of the group containing the type. For instance, types in the Web applications namespace 200 can be referenced using the hierarchical name "System.Web". In this way, the individual namespaces 200, 202, 204, and 206 become major branches off of the System namespace and can carry a designation where the individual namespaces are prefixed with a designator, such as a "System." prefix. The Web applications namespace 200 pertains to Web based functionality, such as dynamically generated Web pages (e.g., Microsoft's Active Server Pages (ASP)). It supplies types that enable browser/server communication. The client applications namespace 202 pertains to drawing and client side UI functionality. It supplies types that enable drawing of two-dimensional (2D), imaging, and printing, as well as the ability to construct window forms, menus, boxes, and so on. The data and XML namespace 204 relates to connectivity to data sources and XML functionality. It supplies classes, interfaces, delegates, and enumerations that enable security, specify data types, and serialize objects into XML format documents or streams. The base class libraries (BCL) namespace 206 pertains to basic system and runtime functionality. It contains the fundamental types and base classes that define commonly-used value and reference data types, events and event handlers, interfaces, attributes, and processing exceptions. In addition to the framework 132, programming tools 210 are provided to assist the developer in building Web services and/or applications. One example of the programming tools 200 is Visual Studio.TM., a multi-language suite of programming tools offered by Microsoft Corporation. Root API Namespaces FIG. 3 shows the API 142 and its four root namespaces in more detail. In one embodiment, the namespaces are identified according to a hierarchical naming convention in which strings of names are concatenated with periods. For instance, the Web applications namespace 200 is identified by the root name "System.Web". Within the "Sytem.Web" namespace is another namespace for Web services, identified as "System.Web.Services", which further identifies another namespace for a description known as "System.Web.Services. Description". With this naming convention in mind, the following provides a general overview of selected namespaces of the API 142, although other naming conventions could be used with equal effect. The Web applications namespace 200 ("System.Web") defines additional namespaces, including: A services namespace 300 ("System.Web.Services") containing classes that enable a developer to build and use Web services. The services namespace 300 defines additional namespaces, including a description namespace 302 ("System.Web. Services. Description") containing classes that enable a developer to publicly describe a Web service via a service description language (such as WSDL, a specification available from the W3C), a discovery namespace 304 ("System.Web. Services.Discovery") containing classes that allow Web service consumers to locate available Web Services on a Web server, and a protocols namespace
306 ("System.Web. Services.Protocols") containing classes that define the protocols used to transmit data across a network during communication between Web service clients and the Web service itself. A caching namespace 308 ("System.Web.Caching") containing classes that enable developers to decrease Web application response time through temporarily caching frequently used resources on the server. This includes ASP.NET pages, web services, and user controls. (ASP.NBT is the updated version of Microsoft's ASP technology.) Additionally, a cache dictionary is available for developers to store frequently used resources, such as hash tables and other data structures. A configuration namespace 310 ("System.Web.Configuration") containing classes that are used to read configuration data in for an application. A UI namespace 312 ("System.Web.UI") containing types that allow developers to create controls and pages that will appear in Web applications as user interfaces on a Web page. This namespace includes the control class, which provides all web based controls, whether those encapsulating HTML elements, higher level Web controls, or even custom User controls, with a common set of functionality. Also provided are classes which provide the web forms server controls data binding functionality, the ability to save the view state of a given control or page, as well as parsing functionality for both programmable and literal controls. Within the UI namespace 312 are two additional namespaces: an HTML controls namespace 314 ("System.Web.UI.HtmlControls") containing classes that permit developers to interact with types that encapsulates html 3.2 elemtents create HTML controls, and a Web controls namespace 316
("System.Web.UI.WeblControls") containing classes that allow developers to create higher level Web controls. A security namespace 318 ("System.Web.Security") containing classes used to implement security in web server applications, such as basic authentication, challenge response authentication, and role based authentication. A session state namespace 320 ("System.Web.SessionState") containing classes used to access session state values (i.e., data that lives across requests for the lifetime of the session) as well as session-level settings and lifetime management methods. The client applications namespace 202 is composed of two namespaces: A windows forms namespace 322 ("System.Windows.Forms") containing classes for creating Windows.RTM.-based client applications that take full advantage of the rich user interface features available in the Microsoft Windows.RTM. operating system, such as the ability to drag and drop screen elements. Such classes may include wrapped APIs available in the Microsoft Windows.RTM. operating system that are used in a windowing UI environment. Within this namespace are a design namespace 324 ("System.Windows.Forms.Design") that contains classes to extend design-time support for Windows forms and a component model namespace 326 ("System.Windows.Forms.ComponentModel") that contains the windows form implementation of the general component model defined in System.ComponentModel. This namespace contains designer tools, such as Visual Studio, which offer a rich experience for developers at design time. A drawing namespace 328 ("System.Drawing") containing classes for graphics functionality. The drawing namespace 328 includes a 2D drawing namespace 330 ("System.Drawing.Drawing2D") that contains classes and enumerations to provide advanced 2-dimmensional and vector graphics functionality, an imaging namespace 332 ("System.Drawing.Imaging") that contains classes for advanced imaging functionality, a printing namespace 334
("System.Drawing.Printing") that contains classes to permit developers to customize printing, and a text namespace 336 ("System.Drawing.Text") that contains classes for advanced typography functionality. The data and XML namespace 204 is composed of two namespaces: A data namespace 340 ("System.Data") containing classes that enable developers to build components that efficiently manage data from multiple data sources. It implements an architecture that, in a disconnected scenario (such as the Internet), provides tools to request, update, and reconcile data in multiple tier systems. The data namespace 340 includes a common namespace 342 that contains types shared by data providers. A data provider describes a collection of types used to access a data source, such as a database, in the managed space. The data namespace 340 also includes an OLE DB namespace 344 that contains types pertaining to data used in object-oriented databases (e.g., Microsoft's SQL Server), and a SQL client namespace 346 that contains types pertaining to data used by SQL clients. The data namespace also includes a SQL types namespace 348 ("System.Data.SqlTypes") that contains classes for native data types within Microsoft's SQL Server. The classes provide a safer, faster alternative to other data types. Using the objects within this namespace helps prevent type conversion errors caused in situations where loss of precision could occur. Because other data types are converted to and from SQL types behind the scenes, explicitly creating and using objects within this namespace results in faster code as well. An XML namespace 350 ("System.XML") containing classes that provide standards-based support for processing XML. The supported standards include XML (e.g., version 1.0), XML Namespaces (both stream level and DOM), XML Schemas, XPath expressions, XSL/T transformations, DOM Level 2 Core, and SOAP (e.g., version 1.1). The XML namespace 350 includes an XSLT namespace 352 ("System.XML.Xsl") that contains classes and enumerations to support XSLT (Extensible Stylesheet Language Transformations), an Xpath namespace 354 ("System.XML.Xpath") that contains an XPath parser and evaluation engine, and a serialization namespace 356 ("System.XML.Serialization") that contains classes used to serialize objects into XML format documents or streams. The base class library namespace 206 ("System") includes the following namespaces: A collections namespace 360 ("System.Collections") containing interfaces and classes that define various collections of objects, such as lists, queues, arrays, hash tables and dictionaries. A configuration namespace 362 ("System.Configuration") containing classes and interfaces that allow developers to programmatically access configuration settings and handle errors in configuration files. A diagnostics namespace 364 ("System.Diagnostics") containing classes that are used to debug applications and to trace code execution. The namespace allows developers to start system processes, read and write to event logs, and monitor system performance using performance counters. A globalization namespace 366 ("System.Globalization") containing classes that define culture-related information, including the language, the country/region, the calendars in use, the format patterns for dates, currency and numbers, and the sort order for strings. An I/O namespace 368 ("System.IO") containing the infrastructure pieces to operate with the intput/output of data streams, files, and directories. This namespace includes a model for working with streams of bytes, higher level readers and writers which consume those bytes, various constructions or implementations of the streams (e.g., FileStream and MemoryStream) and, a set of utility classes for working with files and directories. A net namespace 370 ("System.Net") providing an extensive set of classes for building network-enabled application, referred to as the Net Class Libraries (NCL). One element to the design of the Net Class Libraries is an extensible, layered approach to exposing networking functionality. The NCL stack contains three basic layers. A base layer (System.Net.Socket) provides access to an interface to TCP/IP, the communications protocol of UNIX networks and the Internet. One example of such an interface is the "WinSock API" from Microsoft Corporation. The next layer is the Transport Protocol classes, which support such transport protocols as TCP and UDP. Developers may write their own protocol classes to provide support for protocols such as IGMP and ICMP. The third layer is the Web request, which provides an abstract factory pattern for the creation of other protocol classes. The NCL provides implementations for Hyper Text Transport Protocol (HTTP). A reflection namespace ("System.Reflection") 372 containing types that provide a managed view of loaded types, methods, and fields, with the ability to dynamically create and invoke types. A resources namespace 374
("System.Resources") containing classes and interfaces that allow developers to create, store and manage various culture-specific resources used in an application. A security namespace 376 ("System.Security") supporting the underlying structure of the security system, including interfaces, attributes, exceptions, and base classes for permissions. A service process namespace 378 ("System.ServiceProcess") containing classes that allow developers to install and run services. Services are long-running executables that run without a user interface. They can be installed to run under a system account that enables them to be started at computer reboot. Services whose implementation is derived from processing in one class can define specific behavior for start, stop, pause, and continue commands, as well as behavior to take when the system shuts down. A text namespace 380 ("System.Text") containing classes representing various types of encodings (e.g., ASCII, Unicode, UTF-7, and UTF-8), abstract base classes for converting blocks of characters to and from blocks of bytes, and a helper class that manipulates and formats string objects without creating intermediate instances. A threading namespace 382 ("System.Threading") containing classes and interfaces that enable multi-threaded programming. The threading namespace includes a ThreadPool class that manages groups of threads, a Timer class that enables a delegate to be called after a specified amount of time, and a Mutex class for synchronizing mutually-exclusive threads. This namespace also provides classes for thread scheduling, wait notification, and deadlock resolution. A runtime namespace 384 ("System.Runtime") containing multiple namespaces concerning runtime features, including an interoperation services namespace 386 ("System.Runtime.InteropServices") that contains a collection of classes useful for accessing COM objects. The types in the InteropServices namespace fall into the following areas of functionality: attributes, exceptions, managed definitions of COM types, wrappers, type converters, and the Marshal class. The runtime namespace 384 further includes a remoting namespace 388 ("System.Runtime.Remoting") that contains classes and interfaces allowing developers to create and configure distributed applications. Another namespace within the runtime namespace 384 is a serialization namespace 390 ("System.Runtime.Serialization") that contains classes used for serializing and deserializing objects. Serialization is the process of converting an object or a graph of objects into a linear sequence of bytes for either storage or transmission to another location. The web applications namespace 200 ("System.Web") defines several additional namespaces, including the services namespace 300 ("System.Web.Services"), a caching namespace 308 ("System.Web.Caching"), a configuration namespace 310 ("System.Web.Configuration"), a UI namespace 312 ("System.Web.UI"), a security namespace 318
("System.Web.Security"), and a session state namespace 320 ("System.Web.SessionState"). In general, the web applications namespace 200 supplies tools that enable browser-server communication. The services namespace 300 contains classes that allow developers to build and use various web services. The services namespace includes a web service class that defines a base class for web services and a web method attribute class that allows a method to be programmatically exposed over the web. The UI namespace 312 contains classes that allow a user to create HTML server controls on a web page. These HTML server controls execute on the server and map to standard HTML tags. The UI namespace also contains classes that allow a user to create web server controls on a web page. These web server controls run on the web server and include form controls, such as buttons and text boxes. The web applications namespace 200 also includes classes for manipulating cookies, transferring files, handling exception information, and controlling an output cache. Specific details regarding the System.Web namespace are provided below. System.Web DETX Description The System.Web namespace supplies classes and interfaces that enable browser/server communication. This namespace includes the HTTPRequest class that provides extensive information about the current HTTP request, the HTTPResponse class that manages HTTP output to the client, and the HTTPServerUtility object that provides access to server-side utilities and processes. System.Web also includes classes for cookie manipulation, file transfer, exception information, and output cache control. BeginEventHandler delegate (System.Web) DETX Description EndEventHandler delegate (System.Web) DETX Description HttpWorkerRequest.EndOfSendNotification delegate (System.Web) DETX Description HttpApplication class (System.Web) DETX Description Defines the methods, properties, and events common to all application objects within an ASP.NET application. Constructors: HttpApplication Example Syntax: [C#] public HttpApplication( ); [C++] public: HttpApplication( ); [VB] Public Sub New( ) [JScript] public function HttpApplication( ); Properties: Application [C#] public HttpApplicationState Application {get;} [C++] public: _property HttpApplicationState* get_Application( ); [VB] Public ReadOnly Property Application As HttpApplicationState [JScript] public function get Application( ): HttpApplicationState; DETX Description Gets a reference to an HTTPApplication state bag instance. Context [C#] public HttpContext Context {get;} [C++] public: _property HttpContext* get_Context( ); [VB] Public ReadOnly Property Context As HttpContext [JScript] public function get Context( ): HttpContext; DETX Description Gets the HTTPRuntime--provided context object that provides access to additional pipeline-module exposed objects. Events [C#] protected EventHandlerList Events {get;} [C++] protected: _property EventHandlerList* get_Events( ); [VB] Protected ReadOnly Property Events As EventHandlerList [JScript] protected function get Events( ): EventHandlerList; DETX Description Modules [C#] public HttpModuleCollection Modules {get;} [C++] public: _property HttpModuleCollection* get_Modules( ); [VB] Public ReadOnly Property Modules As HttpModuleCollection [JScript] public function get Modules( ): HttpModuleCollection; DETX Description Gets the collection of HTTPModules configured for the current application. Request [C#] public HttpRequest Request {get;} [C++] public: _property HttpRequest* get_Request( ); [VB] Public ReadOnly Property Request As HttpRequest [JScript] public function get Request( ): HttpRequest; DETX Description Gets the intrinsic object that provides access to incoming HttpRequest data. Response [C#] public HttpResponse Response {get;} [C++] public: _property HttpResponse* get_Response( ); [VB] Public ReadOnly Property Response As HttpResponse [JScript] public function get Response( ): HttpResponse; DETX Description The intrinsic object that allows transmission of HttpResponse data to a client. Server [C#] public HttpServerUtility Server {get;} [C++] public: _property HttpServerUtility* get_Server( ); [VB] Public ReadOnly Property Server As HttpServerUtility [JScript] public function get Server( ): HttpServerUtility; DETX Description Gets the intrinsic Server object. Session [C#] public HttpSessionState Session {get;} [C++] public: _property HttpSessionState* get_Session( ); [VB] Public ReadOnly Property Session As HttpSessionState [JScript] public function get Session( ): HttpSessionState; DETX Description Gets the intrinsic Session object that provides access to session data. Site [C#] public ISite Site {get; set;} [C++] public: _property ISite* get_Site( );public: _property void set_Site(ISite*); [VB] Public Property Site As ISite [JScript] public function get Site( ): ISite;public function set Site(ISite); DETX Description User [C#] public IPrincipal User {get;} [C++] public: _property IPrincipal* get_User( ); [VB] Public ReadOnly Property User As IPrincipal [JScript] public function getUser( ): IPrincipal; DETX Description Gets the User intrinsic object. [C#] public event EventHandler AcquireRequestState; [C++] public: _event EventHandler* AcquireRequestState; [VB] Public Event AcquireRequestState As EventHandler DETX Description [C#] public event EventHandler AuthenticateRequest; [C++] public: _event EventHandler* AuthenticateRequest; [VB] Public Event AuthenticateRequest As EventHandler DETX Description [C#] public event EventHandler AuthorizeRequest; [C++] public: _event EventHandler* AuthorizeRequest; [VB] Public Event AuthorizeRequest As EventHandler DETX Description [C#] public event EventHandler BeginRequest; [C++] public: _event EventHandler* BeginRequest; [VB] Public Event BeginRequest As EventHandler DETX Description [C#] public event EventHandler Disposed; [C++] public: _sealed _event EventHandler* Disposed; [VB] NotOverridable Public Event Disposed As EventHandler DETX Description [C#] public event EventHandler EndRequest; [C++] public: _event EventHandler* EndRequest; [VB] Public Event EndRequest As EventHandler DETX Description [C#] public event EventHandler Error; [C++] public: _event EventHandler* Error; [VB] Public Event Error As EventHandler DETX Description [C#] public event EventHandler PostRequestHandlerExecute; [C++] public: _event EventHandler* PostRequestHandlerExecute; [VB] Public Event PostRequestHandlerExecute As EventHandler DETX Description [C#] public event EventHandler PreRequestHandlerExecute; [C++] public: _event EventHandler* PreRequestHandlerExecute; [VB] Public Event PreRequestHandlerExecute As EventHandler DETX Description [C#] public event EventHandler PreSendRequestContent; [C++] public: _event EventHandler* PreSendRequestContent; [VB] Public Event PreSendRequestContent As EventHandler DETX Description [C#] public event EventHandler PreSendRequestHeaders; [C++] public: _event EventHandler* PreSendRequestHeaders; [VB] Public Event PreSendRequestHeaders As EventHandler DETX Description [C#] public event EventHandler ReleaseRequestState; [C++] public: _event EventHandler* ReleaseRequestState; [VB] Public Event ReleaseRequestState As EventHandler DETX Description [C#] public event EventHandler ResolveRequestCache; [C++] public: _event EventHandler* ResolveRequestCache; [VB] Public Event ResolveRequestCache As EventHandler DETX Description [C#] public event EventHandler UpdateRequestCache; [C++] public: _event EventHandler* UpdateRequestCache; [VB] Public Event UpdateRequestCache As EventHandler DETX Description Methods: AddOnAcquireRequestStateAsync [C#] public void AddOnAcquireRequestStateAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnAcquireRequestStateAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnAcquireRequestStateAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnAcquireRequestStateAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnAuthenticateRequestAsync [C#] public void AddOnAuthenticateRequestAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnAuthenticateRequestAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnAuthenticateRequestAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnAuthenticateRequestAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnAuthorizeRequestAsync [C#] public void AddOnAuthorizeRequestAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnAuthorizeRequestAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnAuthorizeRequestAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnAuthorizeRequestAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnBeginRequestAsync [C#] public void AddOnBeginRequestAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnBeginRequestAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnBeginRequestAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnBeginRequestAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnEndRequestAsync [C#] public void AddOnEndRequestAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnEndRequestAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnEndRequestAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnEndRequestAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnPostRequestHandlerExecuteAsync [C#] public void AddOnPostRequestHandlerExecuteAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnPostRequestHandlerExecuteAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnPostRequestHandlerExecuteAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnPostRequestHandlerExecuteAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnPreRequestHandlerExecuteAsync [C#] public void AddOnPreRequestHandlerExecuteAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnPreRequestHandlerExecuteAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnPreRequestHandlerExecuteAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnPreRequestHandlerExecuteAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnReleaseRequestStateAsync [C#] public void AddOnReleaseRequestStateAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnReleaseRequestStateAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnReleaseRequestStateAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnReleaseRequestStateAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnResolveRequestCacheAsync [C#] public void AddOnResolveRequestCacheAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnResolveRequestCacheAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddOnResolveRequestCacheAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnResolveRequestCacheAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description AddOnUpdateRequestCacheAsync [C#] public void AddOnUpdateRequestCacheAsync(BeginEventHandler bh, EndEventHandler eh); [C++] public: void AddOnUpdateRequestCacheAsync(BeginEventHandler* bh, EndEventHandler* eh); [VB] Public Sub AddonUpdateRequestCacheAsync(ByVal bh As BeginEventHandler, ByVal eh As EndEventHandler) [JScript] public function AddOnUpdateRequestCacheAsync(bh: BeginEventHandler, eh: EndEventHandler); DETX Description CompleteRequest [C#] public void CompleteRequest( ); [C++] public: void CompleteRequest( ); [VB] Public Sub CompleteRequest( ) [JScript] public function CompleteRequest( ); DETX Description Dispose [C#] public virtual void Dispose( ); [C++] public: virtual void Dispose( ); [VB] Overridable Public Sub Dispose( ) [JScript] public function Dispose( ); DETX Description Cleans up the instance variables of an HttpModule. The System.Web.HttpApplication.Request, System.Web.HttpApplication.Response, System.Web.HttpApplication.Session and System.Web.HttpApplication.Application properties are not available for use at the time System.Web.HttpApplication.Dispose is executed. GetVaryByCustomString [C#] public virtual string GetVaryByCustomString(HttpContext context, string custom); [C++] public: virtual String* GetVaryByCustomString(HttpContext* context, String* custom); [VB] Overridable Public Function GetVaryByCustomString(ByVal context As HttpContext, ByVal custom As String) As String [JScript] public function GetVaryByCustomString(context: HttpContext, custom: String): String; DETX Description Init [C#] public virtual void Init( ); [C++] public: virtual void Init( ); [VB] Overridable Public Sub Init( ) [JScript] public function Init( ); DETX Description Initializes HttpModule instance variables and register event handlers with the hosting Application. IHttpAsyncHandler.BeginProcessRequest [C#] IAsyncResult IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, object extraData); [C++] IAsyncResult* IHttpAsyncHandler::BeginProcessRequest(HttpContext* context, AsyncCallback* cb, Object* extraData); [VB] Function BeginProcessRequest(ByVal context As HttpContext, ByVal cb As AsyncCallback, ByVal extraData As Object) As IAsyncResult Implements IHttpAsyncHandler.BeginProcessRequest [JScript] function IHttpAsyncHandler.BeginProcessRequest(context: HttpContext, cb: AsyncCallback, extraData: Object): IAsyncResult; IHttpAsyncHandler.EndProcessRequest [C#] void IHttpAsyncHandler.EndProcessRequest(IAsyncResult result); [C++] void IHttpAsyncHandler::EndProcessRequest(IAsyncResult* result); [VB] Sub EndProcessRequest(ByVal result As IAsyncResult) Implements IHttpAsyncHandler.EndProcessRequest [JScript] function IHttpAsyncHandler.EndProcessRequest(result: IAsyncResult); IHttpHandler.ProcessRequest [C#] void IHttpHandler.ProcessRequest(HttpContext context); [C++] void IHttpHandler::ProcessRequest(HttpContext* context); [VB] Sub ProcessRequest(ByVal context As HttpContext) Implements IHttpHandler.ProcessRequest [JScript] function IHttpHandler.ProcessRequest(context: HttpContext); HttpApplicationState class (System.Web) ToString DETX Description Enables sharing of global information across multiple sessions and requests within an ASP.NET application. An ASP.NET application is the sum of all files, pages, handlers, modules, and code within the scope of a virtual directory and its subdirectories on a single web server. AllKeys ToString [C#] public string[ ] AllKeys {get;} [C++] public: _property String* get_AllKeys( ); [VB] Public ReadOnly Property AllKeys As String( ) [JScript] public function get AllKeys( ): String[ ]; DETX Description Gets the access keys in the System.Web.HttpApplicationState collection. Contents ToString [C#] public HttpApplicationState Contents {get;} [C++] public: _property HttpApplicationState* get_Contents( ); [VB] Public ReadOnly Property Contents As HttpApplicationState [JScript] public function get Contents( ): HttpApplicationState; DETX Description Gets a reference to the System.Web.HttpApplicationState object. This property provides compatibility with earlier versions of ASP. Count ToString [C#] public override int Count {get;} [C++] public: _property virtual int get_Count( ); [VB] Overrides Public ReadOnly Property Count As Integer [JScript] public function get Count( ): int; DETX Description Gets the number of objects in the System.Web.HttpApplicationState collection. IsReadOnly Item ToString System.Web.HttpApplicationState DETX Description Gets the value of a single System.Web.HttpApplicationState object by name. The name of the object in the collection. Item ToString [C#] public object this[int index] {get;} [C++] public: _property Object* get_Item(int index); [VB] Public Default ReadOnly Property Item(ByVal index As Integer) As Object [JScript] returnValue=HttpApplicationStateObject.Item(index); DETX Description Gets a single System.Web.HttpApplicationState object by index. The numerical index of the object in the collection. Keys StaticObjects ToString DETX Description Gets all objects declared via an tag within the ASP.NET application. Application objects are defined in the Global.asax file. Add [C#] public void Add(string name, object value); [C++] public: void Add(String* name, Object* value); [VB] Public Sub Add(ByVal name As String, ByVal value As Object) [JScript] public function Add(name: String, value: Object); DETX Description Adds a new object to the System.Web.HttpApplicationState collection. The name of the object to be added to the collection. The value of the object. Clear [C#] public void Clear( ); [C++] public: void Clear( ); [VB] Public Sub Clear( ) [JScript] public function Clear( ); DETX Description Removes all objects from an System.Web.HttpApplicationState collection. Get [C#] public object Get(int index); [C++] public: Object* Get(int index); [VB] Public Function Get(ByVal index As Integer) As Object [JScript] public function Get(index: int): Object; DETX Description Gets an System.Web.HttpApplicationState object by numerical index. Return Value: The object referenced by index. The index of the application state object. Get [C#] public object Get(string name); [C++] public: Object* Get(String* name); [VB] Public Function Get(ByVal name As String) As Object [JScript] public function Get(name: String): Object; Gets an System.Web.HttpApplicationState object by name or index. DETX Description Gets an System.Web.HttpApplicationState object by name. Return Value: The object referenced by name. The following example returns an object named MyAppVarl from the System.Web.HttpApplicationState collection of the intrinsic System.Web.HttpContext.Application object and copies it to a new object variable. The name of the object. GetKey [C#] public string GetKey(int index); [C++] public: String* GetKey(int index); [VB] Public Function GetKey(ByVal index As Integer) As String [JScript] public function GetKey(index: int): String; DETX Description Gets an System.Web.HttpApplicationState object name by index. Return Value: The name under which the application state object was saved. The index of the application state object. Lock [C#] public void Lock( ); [C++] public: void Lock( ); [VB] Public Sub Lock( ) [JScript] public function Lock( ); DETX Description Locks access to an System.Web.HttpApplicationState variable to facilitate access synchronization. Remove [C#] public void Remove(string name); [C++] public: void Remove(String* name); [VB] Public Sub Remove(ByVal name As String) [JScript] public function Remove(name: String); DETX Description Removes the named object from an System.Web.HttpApplicationState collection. The name of the object to be removed from the collection. RemoveAll [C#] public void RemoveAll( ); [C++] public: void RemoveAll( ); [VB] Public Sub RemoveAll( ) [JScript] public function RemoveAll( ); DETX Description Removes all objects from an System.Web.HttpApplicationState collection. System.Web.HttpApplicationState.RemoveAll is an internal call to System.Web.HttpApplicationState.Clear. RemoveAt [C#] public void RemoveAt(int index); [C++] public: void RemoveAt(int index); [VB] Public Sub RemoveAt(ByVal index As Integer) [JScript] public function RemoveAt(index: int); Removes an object from the application state collection by name. Set [C#] public void Set(string name, object value); [C++] public: void Set(String* name, Object* value); [VB] Public Sub Set(ByVal name As String, ByVal value As Object) [JScript] public function Set(name: String, value: Object); DETX Description Updates the value of an object in an System.Web.HttpApplicationState collection. The name of the object to be updated. The updated value of the object. UnLock [C#] public void UnLock( ); [C++] public: void UnLock( ); [VB] Public Sub UnLock( ) [JScript] public function UnLock( ); DETX Description Unlocks access to an System.Web.HttpApplicationState variable to facilitate access synchronization. HttpBrowserCapabilities class (System.Web) UnLock DETX Description Enables the server to gather information on the capabilities of the browser that is running on the client. System.Web.HttpBrowserCapabilities properties are accessible through the System.Web.HttpRequest.Browser property of ASP.NET's intrinsic System.Web.HttpContext.Request object. HttpBrowserCapabilities Example Syntax: UnLock [C#] public HttpBrowserCapabilities( ); [C++] public: HttpBrowserCapabilities( ); [VB] Public Sub New( ) [JScript] public function HttpBrowserCapabilities( ); ActiveXControls UnLock [C#] public bool ActiveXControls {get;} [C++] public: _property bool get_ActiveXControls( ); [VB] Public ReadOnly Property ActiveXControls As Boolean [JScript] public function get ActiveXControls( ): Boolean; DETX Description Gets a value indicating whether the client browser supports ActiveX controls. AOL UnLock [C#] public bool AOL {get;} [C++] public: _property bool get_AOL( ); [VB] Public ReadOnly Property AOL As Boolean [JScript] public function get AOL( ): Boolean; DETX Description Gets a value indicating whether the client is an America Online (AOL) browser. BackgroundSounds UnLock [C#] public bool BackgroundSounds {get;} [C++] public: _property bool get_BackgroundSounds( ); [VB] Public ReadOnly Property BackgroundSounds As Boolean [JScript] public function get BackgroundSounds( ): Boolean; DETX Description Gets a value indicating whether the client browser supports background sounds. Beta UnLock [C#] public boot Beta {get;} [C++] public: _property boot get_Beta( ); [VB] Public ReadOnly Property Beta As Boolean [JScript] public function get Beta( ): Boolean; DETX Description Gets a value indicating whether the browser is a beta release. Browser UnLock [C#] public string Browser {get;} [C++] public: _property String* get_Browser( ); [VB] Public ReadOnly Property Browser As String [JScript] public function get Browser( ): String; DETX Description Gets the browser string (if any) that was transmitted in the User-Agent header. CDF UnLock [C#] public bool CDF {get;} [C++] public: _property bool get_CDF( ); [VB] Public ReadOnly Property CDF As Boolean [JScript] public function get CDF( ): Boolean; DETX Description Gets a value indicating whether the client browser supports Channel Definition Format (CDF) for webcasting. CirVersion UnLock [C#] public Version CirVersion {get;} [C++] public: _Property Version* get_ClrVersion( ); [VB] Public ReadOnly Property ClrVersion As Version [JScript] public function get ClrVersion( ): Version; DETX Description Gets the version number of the NET common language runtime that the client browser supports. If no common language runtime version is specified, the property value is 0, 0, -1, -1.

Cookies UnLock [C#] public bool Cookies {get;} [C++] public: _property bool get_Cookies( ); [VB] Public ReadOnly Property Cookies As Boolean [JScript] public function get Cookies( ): Boolean; DETX Description Gets a value indicating whether the client browser supports cookies. Crawler UnLock [C#] public bool Crawler {get;} [C++] public: _property bool get_Crawler( ); [VB] Public ReadOnly Property Crawler As Boolean [JScript] public function get Crawler( ): Boolean; DETX Description Gets a value indicating whether the client browser is a Web crawler search engine. EcmaScriptVersion UnLock [C#] public Version EcmaScriptVersion {get;} [C++] public: _property Version* get_EcmaScriptVersion( ); [VB] Public ReadOnly Property EcmaScriptVersion As Version [JScript] public function get EcmaScriptVersion( ): Version; DETX Description Gets the version number of ECMA script that the client browser supports. The European Computer Manufacturer's Association develops standards for information and communication systems. For more information, see ECMA's official Web site at http://www.ecma.ch. Frames UnLock [C#] public bool Frames {get;} [C++] public: _property bool get_Frames( ); [VB] Public ReadOnly Property Frames As Boolean [JScript] public function get Frames( ): Boolean; DETX Description Gets a value indicating whether the client browser supports HTML frames. Item JavaApplets UnLock DETX Description Gets a value indicating whether the client browser supports Java applets. JavaScript UnLock [C#] public bool JavaScript {get;} [C++] public: _property bool get_JavaScript( ); [VB] Public ReadOnly Property JavaScript As Boolean [JScript] public function get JavaScript( ): Boolean; DETX Description Gets a value indicating whether the client browser supports JavaScript. MajorVersion UnLock [C#] public int MajorVersion {get;} [C++] public: _property int get_MajorVersion( ); [VB] Public ReadOnly Property MajorVersion As Integer [JScript] public function get MajorVersion( ): int; DETX Description Gets the major (that is, integer) version number of the client browser. MinorVersion UnLock [C#] public double MinorVersion {get;} [C++] public: _property double get_MinorVersion( ); [VB] Public ReadOnly Property MinorVersion As Double [JScript] public function get MinorVersion( ): double; DETX Description Gets the minor (that is, decimal) version number of the client browser. MSDomVersion UnLock [C#] public Version MSDomVersion {get;} [C++] public: _property Version* get_MSDomVersion( ); [VB] Public ReadOnly Property MSDomVersion As Version [JScript] public function get MSDomVersion( ): Version; DETX Description Gets the version of Microsoft HTML (MSHTML) Document Object Model (DOM) that the client browser supports. Platform UnLock [C#] public string Platform {get;} [C++] public: _property String* get_Platform( ); [VB] Public ReadOnly Property Platform As String [JScript] public function get Platform( ): String; DETX Description Gets the name of the platform that the client uses. Some possible Platform values are: Unknown, Win95, Win98, WinNT (which includes Windows 2000), Win16, WinCE, Mac68K, MacPPC, UNIX, and WebTV. Tables UnLock [C#] public bool Tables {get;} [C++] public: _property bool get_Tables( ); [VB] Public ReadOnly Property Tables As Boolean [JScript] public function get Tables( ): Boolean; DETX Description Gets a value indicating whether the client browser supports HTML tables. TagWriter UnLock [C#] public Type TagWriter {get;} [C++] public: _property Type* get_TagWriter( ); [VB] Public ReadOnly Property TagWriter As Type [JScript] public function get TagWriter( ): Type; DETX Description Type UnLock [C#] public string Type {get;} [C++] public: _property String* get_Type( ); [VB] Public ReadOnly Property Type As String [JScript] public function get Type( ): String; DETX Description Gets the name and major (that is, integer) version number of the client browser. VBScript UnLock [C#] public bool VBScript {get;} [C++] public: _property bool get_VBScript( ); [VB] Public ReadOnly Property VBScript As Boolean [JScript] public function get VBScript( ): Boolean; DETX Description Gets a value indicating whether the client browser supports VBScript. Version UnLock [C#] public string Version {get;} [C++] public: _property String* get_Version( ); [VB] Public ReadOnly Property Version As String [JScript] public function get Version( ): String; DETX Description Gets the full (integer and decimal) version number of the client browser. W3CDomVersion UnLock [C#] public Version W3CDomVersion {get;} [C++] public: _property Version* get_W3CDomVersion( ); [VB] Public ReadOnly Property W3CDomVersion As Version [JScript] public function get W3CDomVersion( ): Version; DETX Description Gets the version of the World Wide Web Consortium (W3C) XML Document Object Model (DOM) that the client browser supports. Win16 UnLock [C#] public bool Win16 {get;} [C++] public: _property bool get_Win16( ); [VB] Public ReadOnly Property Win16 As Boolean [JScript] public function get Win16( ): Boolean; DETX Description Gets a value indicating whether the client is a Win16-based machine. Win32 UnLock [C#] public bool Win32 {get;} [C++] public: _property bool get_Win32( ); [VB] Public ReadOnly Property Win32 As Boolean [JScript] public function get Win32( ): Boolean; DETX Description Gets a value indicating whether the client is a Win32-based machine. HttpCacheability enumeration (System.Web) ToString DETX Description Provides enumerated values that are used to set the Cache-Control HTTP header. ToString [C#] public const HttpCacheability NoCache; [C++] public: const HttpCacheability NoCache; [VB] Public Const NoCache As HttpCacheability [JScript] public var NoCache: HttpCacheability; DETX Description Sets the Cache-Control: no-cache header. Without a field name, the directive applies to the entire request and a shared (proxy server) cache must force a successful revalidation with the origin Web server before satisfying the request. With a field name, the directive applies only to the named field;the rest of the response may be supplied from a shared cache. ToString [C#] public const HttpCacheability Private; [C++] public: const HttpCacheability Private; [VB] Public Const Private As HttpCacheability [JScript] public var Private: HttpCacheability; DETX Description Default value. Sets Cache-Control: private to specify that the response is cacheable only on the client and not by shared (proxy server) caches. ToString [C#] public const HttpCacheability Public; [C++] public: const HttpCacheability Public; [VB] Public Const Public As HttpCacheability [JScript] public var Public: HttpCacheability; DETX Description Sets Cache-Control: public to specify that the response is cacheable by clients and shared (proxy) caches. ToString [C#] public const HttpCacheability Server; [C++] public: const HttpCacheability Server; [VB] Public Const Server As HttpCacheability [JScript] public var Server: HttpCacheability; DETX Description Specifies that the response is cached only at the origin server. Similar to the NoCache option. Clients receive a Cache-Control: no-cache directive but the document is cached on the origin server. HttpCachePolicy class (System.Web) ToString DETX Description Contains methods for setting cache-specific HTTP headers and for controlling the ASP.NET page output cache. For background information on HTTP headers and controlling caching, see the document RFC 2616: Hypertext Transfer Protocol--HTTP/1.1, available on the World Wide Web Consortium's site at http://www.w3c.org. VaryByHeaders ToString [C#] public HttpCacheVaryByHeaders VaryByHeaders {get;} [C++] public: _property HttpCacheVaryByHeaders* get_VaryByHeaders( ); [VB] Public ReadOnly Property VaryByHeaders As HttpCacheVaryByHeaders [JScript] public function get VaryByHeaders( ): HttpCacheVaryByHeaders; DETX Description Gets the list of all HTTP headers that will be used to vary cache output. When a cached item has several vary headers, a separate version of the requested document is available from the cache for each HTTP header type. VaryByParams ToString [C#] public HttpCacheVaryByParams VaryByParams {get;} [C++] public: _property HttpCacheVaryByParams* get_VaryByParams( ); [VB] Public ReadOnly Property VaryByParams As HttpCacheVaryByParams [JScript] public function get VaryByParams( ): HttpCacheVaryByParams; DETX Description Gets the list of parameters received by a GET (querystring) or POST (in the body of the HTTP request) that affect caching. For each named parameter in VaryByParams a separate version of the requested document is available from the cache, the version varying by the parameter's value. AddValidationCallback [C#] public void AddValidationCallback(HttpCacheValidateHandler handler, object data); [C++] public: void AddValidationCallback(HttpCacheValidateHandler* handler, Object* data); [VB] Public Sub AddValidationCallback(ByVal handler As HttpCacheValidateHandler, ByVal data As Object) [JScript] public function AddValidationCallback(handler: HttpCacheValidateHandler, data: Object); DETX Description Registers a validation callback for the current response. AddValidationCallback provides a mechanism to programmatically check the validity of a item in the cache before the item is returned from the cache. The System.Web.HttpCacheValidateHandler value. The arbitrary user-supplied data that is passed back to the AddValidationCallback delegate. AppendCacheExtension [C#] public void AppendCacheExtension(string extension); [C++] public: void AppendCacheExtension(String* extension); [VB] Public Sub AppendCacheExtension(ByVal extension As String) [JScript] public function AppendCacheExtension(extension: String); DETX Description Appends the specified text to the Cache-Control HTTP header. If the browser does not recognize cache control directives or extensions, the browser must ignore the unrecognized terms. For more information, see the document RFC 2616: Hypertext Transfer Protocol--HTTP/1.1, available on the World Wide Web Consortium's site at http://www.w3c.org. The text to append to the Cache-Control header. SetCacheability [C#] public void SetCacheability(HttpCacheability cacheability); [C++] public: void SetCacheability(HttpCacheability cacheability); [VB] Public Sub SetCacheability(ByVal cacheability As HttpCacheability) [JScript] public function SetCacheability(cacheability: HttpCacheability); Sets the Cache-Control HTTP header. The Cache-Control HTTP header controls how documents are to be cached on the network. DETX Description Sets the Cache-Control header to one of the values of System.Web.HttpCacheability. An System.Web.HttpCacheability enumeration value. SetCacheability [C#] public void SetCacheability(HttpCacheability cacheability, string field); [C++] public: void SetCacheability(HttpCacheability cacheability, String* field); [VB] Public Sub SetCacheability(ByVal cacheability As HttpCacheability, ByVal field As String) [JScript] public function SetCacheability(cacheability: HttpCacheability, field: String); DETX Description Sets the Cache-Control header to one of the values of System.Web.HttpCacheability and appends an extension to the directive. The field name extension is valid only when used with the private or no-cache directives. For more information, see the document RFC 2616: Hypertext Transfer Protocol--HTTP/1.1, available on the World Wide Web Consortium's site at http://www.w3c.org. The System.Web.HttpCacheability enumeration value to set the header to. The cache control extension to add to the header. SetETag [C#] public void SetETag(string etag); [C++] public: void SetETag(String* etag); [VB] Public Sub SetETag(ByVal etag As String) [JScript] public function SetETag(etag: String); DETX Description Sets the ETag HTTP header to the specified string. The ETag header is a unique identifier for a specific version of a document. Once an ETag header is set, subsequent attempts to set it will fail and an exception will be thrown. The text to use for the ETag header. SetETagFromFileDependencies [C#] public void SetETagFromFileDependencies( ); [C++] public: void SetETagFromFileDependencies( ); [VB] Public Sub SetETagFromFileDependencies( ) [JScript] public function SetETagFromFileDependencies( ); DETX Description Sets the ETag HTTP header based on the time stamps of the handler's file dependencies. SetEtagFromFileDependencies sets the ETag header by retrieving the last modified time stamps of all files on which the handler is dependent, combining all file names and time stamps into a single string, then hashing that string into a single digest that is used as the ETag. SetExpires [C#] public void SetExpires(DateTime date); [C++] public: void SetExpires(DateTime date); [VB] Public Sub SetExpires(ByVal date As DateTime) [JScript] public function SetExpires(date: DateTime); DETX Description Sets the Expires HTTP header to an absolute date and time. This method will fail if the expiration date violates the principle of restrictiveness. The absolute System.DateTime value to set the Expiresheader to. SetLastModified [C#] public void SetLastModified(DateTime date); [C++] public: void SetLastModified(DateTime date); [VB] Public Sub SetLastModified(ByVal date As DateTime) [JScript] public function SetLastModified(date: DateTime); DETX Description Sets the Last-Modified HTTP header to the System.DateTime value supplied. The Last-Modified HTTP header time stamps the document with the DateTime value indicating when the document was last modified. The new System.DateTime value for the Last-Modified header. SetLastModifiedFromFileDependencies [C#] public void SetLastModifiedFromFileDependencies( ); [C++] public: void SetLastModifiedFromFileDependencies( ); [VB] Public Sub SetLastModifiedFromFileDependencies( ) [JScript] public function SetLastModifiedFromFileDependencies( ); DETX Description Sets the Last-Modified HTTP header based on the time stamps of the handler's file dependencies. SetMaxAge [C++] public void SetMaxAge(TimeSpan delta); [C++] public: void SetMaxAge(TimeSpan delta); [VB] Public Sub SetMaxAge(ByVal delta As TimeSpan) [JScript] public function SetMaxAge(delta: TimeSpan); DETX Description Sets the Cache-Control: max-age HTTP header based on the specified time span. Max-age is the maximum absolute time a document is allowed to exist before being considered stale. The time span used to set the Cache-Control: max-age header. SetNoServerCaching [C#] public void SetNoServerCaching( ); [C++] public: void SetNoServerCaching( ); [VB] Public Sub SetNoServerCaching( ) [JScript] public function SetNoServerCaching( ); DETX Description Stops all origin-server caching for the current response. Explicitly denies caching of the document on the origin-server. Once set, all requests for the document are fully processed. When this method is invoked, caching cannot be reenabled for the current response. SetNoStore [C#] public void SetNoStore( ); [C++] public: void SetNoStore( ); [VB] Public Sub SetNoStore( ) [JScript] public function SetNoStore( ); DETX Description Sets the Cache-Control: no-store directive. SetNoTransforms [C#] public void SetNoTransforms( ); [C++] public: void SetNoTransforms( ); [VB] Public Sub SetNoTransforms( ) [JScript] public function SetNoTransforms( ); DETX Description Sets the CacheControl: no-transform directive. The no-transform CacheControl setting instructs network caching applications to not modify the document. SetProxyMaxAge [C#] public void SetProxyMaxAge(TimeSpan delta); [C++] public: void SetProxyMaxAge(TimeSpan delta); [VB] Public Sub SetProxyMaxAge(ByVal delta As TimeSpan) [JScript] public function SetProxyMaxAge(delta: TimeSpan); DETX Description Sets the Cache-Control: s-maxage HTTP header based on the specified time span. System.Web.HttpCachePolicy.SetProxyMaxAge(System.TimeSpan) does not use sliding expiration and will fail if the expiration date violates the principle of restrictiveness. The time span used to set the Cache-Control: s-maxage header. SetRevalidation [C#] public void SetRevalidation(HttpCacheRevalidation revalidation); [C++] public: void SetRevalidation(HttpCacheRevalidation revalidation); [VB] Public Sub SetRevalidation(ByVal revalidation As HttpCacheRevalidation) [JScript] public function SetRevalidation(revalidation: HttpCacheRevalidation); DETX Description Sets the Cache-Control HTTP header to either the must-revalidate or the proxy-revalidate directives based on the supplied enumeration value. The default is to send neither directive in a header unless explicitly specified by this method. The System.Web.HttpCacheRevalidation enumeration value to set the Cache-Control header to. SetSlidingExpiration [C++] public void SetSlidingExpiration(bool slide); [C++] public: void SetSlidingExpiration(bool slide); [VB] Public Sub SetSlidingExpiration(ByVal slide As Boolean) [JScript] public function SetSlidingExpiration(slide: Boolean); DETX Description Sets cache expiration to sliding. When cache expiration is set to sliding, the Cache-Control HTTP header will be renewed with each response. This expiration mode is identical to the IIS configuration option to add an expiration header to all output set relative to the current time. true or false. SetValidUntilExpires [C#] public void SetValidUntilExpires(bool validUntilExpires); [C++] public: void SetValidUntilExpires(bool validUntilExpires); [VB] Public Sub SetValidUntilExpires(ByVal validUntilExpi res As Boolean) [JScript] public function SetValidUntilExp ires(validUntilExpires: Boolean); DETX Description SetVaryByCustom [C#] public void SetVaryByCustom(string custom); [C++] public: void SetVaryByCustom(String* custom); [VB] Public Sub SetVaryByCustom(ByVal custom As String) [JSCript] public function SetVaryByCustom(custom: String); DETX Description Sets the Vary HTTP header to the specified text string. The text to set the Vary header to. HttpCacheRevalidation enumeration (System.Web) ToString DETX Description Provides enumerated values that are used to set revalidation-specific Cache-Control HTTP headers. ToString [C#] public const HttpCacheRevalidation AllCaches; [C++] public: const HttpCacheRevalidation AllCaches; [VB] Public Const AllCaches As HttpCacheRevalidation [JScript] public var AllCaches: HttpCacheRevalidation; DETX Description Sets the Cache-Control: must-revalidate HTTP header. ToString [C#] public const HttpCacheRevalidation None; [C++] public: const HttpCacheRevalidation None; [VB] Public Const None As HttpCacheRevalidation [JScript] public var None: HttpCacheRevalidation; DETX Description Default value. If this value is set, no cache-revalidation directive is sent. ToString [C#] public const HttpCacheRevalidation ProxyCaches; [C++] public: const HttpCacheRevalidation ProxyCaches; [VB] Public Const ProxyCaches As HttpCacheRevalidation [JScript] public var ProxyCaches: HttpCacheRevalidation; DETX Description Sets the Cache-Control: proxy-revalidate HTTP header. HttpCacheValidateHandler delegate (System.Web) ToString DETX Description Delegate method that is called when a cached item is validated. Cache items invalidated within the method are treated as cache misses. The System.Web.HttpContext object containing information about the current request. User-supplied data used to validate the cached item. A System.Web.HttpValidationStatus enumeration value. If any handler invalidates the cached item, the item is evicted from the cache and the request is handled as a cache miss. HttpCacheVaryByHeaders class (System.Web) ToString DETX Description Provides a type-safe way to set the Vary HTTP header. The Vary header indicates the request-header fields that the server uses to determine which of multiple cached responses is sent in response to a client request. AcceptTypes ToString [C#] public bool AcceptTypes {get; set;} [C++] public: _property bool get_AcceptTypes( );public: _property void set_AcceptTypes(bool); [VB] Public Property AcceptTypes As Boolean [JScript] public function get AcceptTypes( ): Boolean;public function set AcceptTypes(Boolean); DETX Description Gets or sets a value indicating whether the origin server adds the Accept field to the Vary HTTP header. The Vary header indicates the request-header fields that the server uses to determine which of multiple cached responses is sent in response to a client request. The Accept field specifies that the server selects the response based on the media types acceptable to the client. Item ToString [C#] public bool this[string header] {get; set;} [C++] public: _property bool get_Item(String* header);public: _property void set_Item(String* header, bool); [VB] Public Default Property Item(ByVal header As String) As Boolean [JScript] returnValue=HttpCacheVaryByHeadersObject.Item(header);HttpCacheV- aryByHeadersObject.Item(header)=returnValue; DETX Description Gets or sets a value indicating whether the origin server should add a custom field to the Vary HTTP header. The Vary header indicates the request-header fields that the server uses to determine which of multiple cached responses is sent in response to a client request. The name of the custom header. UserAgent ToString [C#] public bool UserAgent {get; set;} [C++] public: _property bool get_UserAgent( );public: _property void set_UserAgent(bool); [VB] Public Property UserAgent As Boolean [JScript] public function get UserAgent( ): Boolean;public function set UserAgent(Boolean); DETX Description Gets or sets a value indicating whether the origin server adds the User-Agent field to the Vary HTTP header. The Vary header indicates the request-header fields that the server uses to determine which of multiple cached responses is sent in response to a client request. The User-Agent field specifies that the server selects the response based on the type of client user-agent. UserCharSet ToString [C#] public bool UserCharSet {get; set;} [C++] public: _property bool get_UserCharSet( );public: _property void set_UserCharSet(bool); [VB] Public Property UserCharSet As Boolean [JScript] public function get UserCharSet( ): Boolean;public function set UserCharSet(Boolean); DETX Description Gets or sets a value indicating whether the origin server should add the Accept-Charset field to the Vary HTTP header. The Vary header indicates the request-header fields that the server uses to determine which of multiple cached responses is sent in response to a client request. The Accept-CharSet field specifies that the server selects the response based on the client's character set. UserLanguage ToString [C#] public bool UserLanguage {get; set;} [C++] public: _property bool get_UserLanguage( );public: _property void set_UserLanguage(bool); [VB] Public Property UserLanguage As Boolean [JScript] public function get UserLanguage( ): Boolean;public function set UserLanguage(Boolean); DETX Description Gets or sets a value indicating whether the origin server adds the Accept-Language field to the Vary HTTP header. The Vary header indicates the request-header fields that the server uses to determine which of multiple cached responses is sent in response to a client request. The Accept-Language field specifies that the server selects the response based on languages acceptable to the client. VaryByUnspecifiedParameters [C#] public void VaryByUnspecifiedParameters( ); [C++] public: void VaryByUnspecifiedParameters( ); [VB] Public Sub VaryByUnspecifiedParameters( ) [JScript] public function VaryByUnspecifiedParameters( ); DETX Description Sets the Vary HTTP header to the value * (an asterisk) and causes all other Vary header information to be dropped. The Vary header indicates the request-header fields that the server uses to determine which of multiple cached responses is sent in response to a client request. The * field specifies that the server selects the response based on parameters not specified in request headers (for example, the network address of the client). HttpCacheVaryByParams class (System.Web) VaryByUnspecifiedParameters DETX Description Indicates that a cache should contain multiple representations (cached responses) for a particular URI. This class is an encapsulation that provides a type-safe way to set the Vary HTTP header. For more information on HTTP cache control headers, see RFC 2616: Hypertext Transfer Protocol--HTTP/1.1, available on the World Wide Web Consortium's Web site at http://www.w3c.org. See section 14, "Header Field Definitions", for complete details. IgnoreParams VaryByUnspecifiedParameters [C#] public bool IgnoreParams {get; set;} [C++] public: _property bool get_IgnoreParams( );public: _property void set_IgnoreParams(bool); [VB] Public Property IgnoreParams As Boolean [JScript] public function get IgnoreParams( ): Boolean;public function set IgnoreParams(Boolean); DETX Description Gets or sets a value indicating whether HTTP header cache control parameters are ignored. Item VaryByUnspecifiedParameters [C#] public bool this[string header] {get; set;} [C++] public: _property bool get_Item(String* header);public: _property void set_Item(String* header, bool); [VB] Public Default Property Item(ByVal header As String) As Boolean [JScript] returnValue=HttpCacheVaryByParamsObject.Item(header);HttpCacheVa- ryByParamsObject.Item(header)=returnValue; DETX Description Gets or sets the name of the cache-control header that is used to select one of several different cached responses. The name of the custom header. HttpClientCertificate class (System.Web) ToString DETX Description The HttpClientCertificate collection retrieves the certification fields (specified in the X.509 standard) from a request issued by the Web browser. AllKeys BinaryIssuer ToString DETX Description CertEncoding ToString [C#] public int CertEncoding {get;} [C++] public: _property int get_CertEncoding( ); [VB] Public ReadOnly Property CertEncoding As Integer [JScript] public function get CertEncoding( ): int; DETX Description Certificate ToString [C#] public byte[ ] Certificate {get;} [C++] public: _property unsigned char get_Certificate( ); [VB] Public ReadOnly Property Certificate As Byte( ) [JScript] public function get Certificate( ): Byte[ ]; DETX Description A string containing the binary stream of the entire certificate content in ASN.1 format. Cookie ToString [C#] public string Cookie {get;} [C++] public: _property String* get_Cookie( ); [VB] Public ReadOnly Property Cookie As String [JScript] public function get Cookie( ): String; DETX Description Count Flags ToString DETX Description A set of flags that provide additional client certificate information. IsPresent ToString [C#] public bool IsPresent {get;} [C++] public: _property bool get_IsPresent( ); [VB] Public ReadOnly Property IsPresent As Boolean [JScript] public function get IsPresent( ): Boolean; DETX Description IsReadOnly Issuer ToString DETX Description A string that contains a list of subfield values containing information about the certificate issuer. IsValid ToString [C#] public bool IsValid {get;} [C++] public: _property bool get_IsValid( ); [VB] Public ReadOnly Property IsValid As Boolean [JScript] public function get IsValid( ): Boolean; DETX Description Item Item Keys KeySize ToString DETX Description PublicKey ToString [C#] public byte[ ] PublicKey {get;} [C++] public: _property unsigned char get_PublicKey( ); [VB] Public ReadOnly Property PublicKey As Byte( ) [JScript] public function get PublicKey( ): Byte[ ]; DETX Description SecretKeySize ToString [C#] public int SecretKeySize {get;} [C++] public: _property int get_SecretKeySize( ); [VB] Public ReadOnly Property SecretKeySize As Integer [JScript] public function get SecretKeySize( ): int; DETX Description SerialNumber ToString [C#] public string SerialNumber {get;} [C++] public: _property String* get_SerialNumber( ); [VB] Public ReadOnly Property SerialNumber As String [JScript] public function get SerialNumber( ): String; DETX Description A string that contains the certification serial number as an ASCII representation of hexadecimal bytes separated by hyphens (-). For example, 04-67-F3-02. ServerIssuer ToString [C#] public string ServerIssuer {get;} [C++] public: _property String* get_ServerIssuer( ); [VB] Public ReadOnly Property ServerIssuer As String [JScript] public function get ServerIssuer( ): String; DETX Description ServerSubject ToString [C#] public string ServerSubject {get;} [C++] public: _property String* get_ServerSubject( ); [VB] Public ReadOnly Property ServerSubject As String [JScript] public function get ServerSubject( ): String; DETX Description Subject ToString [C#] public string Subject {get;} [C++] public: _property String* get_Subject( ); [VB] Public ReadOnly Property Subject As String [JScript] public function get Subject( ): String; DETX Description A string that contains a list of subfield values that contain information about the subject of the certificate. If this value is specified without a SubField, the ClientCertificate collection returns a comma-separated list of subfields. For example, C=US, O=Msft, and so on. ValidFrom ToString [C#] public DateTime ValidFrom {get;} [C++] public: _property DateTime get_ValidFrom( ); [VB] Public ReadOnly Property ValidFrom As DateTime [JScript] public function get ValldFrom( ): DateTime; DETX Description A date specifying when the certificate becomes valid. This date varies with international settings. ValidUntil ToString [C#] public DateTime ValidUntil {get;} [C++] public: _property DateTime get_ValidUntil( ); [VB] Public ReadOnly Property ValidUntil As DateTime [JScript] public function get ValidUntil( ): DateTime; DETX Description A date specifying when the certificate expires. The year value is displayed as a four-digit number. Get [C#] public override string Get(string field); [C++] public: String* Get(String* field); [VB] Overrides Public Function Get(ByVal field As String) As String [JScript] public override function Get(field: String): String; DETX Description Allows access to individual items in the collection by name. The name of the item in the collection to retrieve. HttpCompileException class (System.Web) ToString DETX Description The exception that is thrown when a compiler error occurs. HttpCompileException Example Syntax: ToString [C#] public HttpCompileException(CompilerResults results, string sourceCode); [C++] public: HttpCompileException(CompilerResults* results, String* sourceCode); [VB] Public Sub New(ByVal results As CompilerResults, ByVal sourceCode As String) [JScript] public function HttpCompileException(results: CompilerResults, sourceCode: String); DETX Description Initializes a new instance of the System.Web.HttpCompileException class. A System.CodeDom.Compiler.CompilerResults containing compiler output and error information. The name of the file being compiled when the error occurs. ErrorCode HelpLink HResult InnerException Message Results ToString DETX Description Gets compiler output and error information for the exception. Source SourceCode ToString DETX Description Gets the name of the source file being compiled when the error occurs. StackTrace TargetSite HttpContext class (System.Web) ToString DETX Description Encapsulates all HTTP-specific information about an individual HTTP request. Classes that inherit the System.Web.IHttpModule and System.Web.IHttpHandler interfaces are provided a reference to an HttpContext object for the current HTTP request. The object provides access to the intrinsic System.Web.HttpContext.Request, System.Web.HttpContext.Response, and System.Web.HttpContext.Server objects for the request. HttpContext Example Syntax: ToString [C#] public HttpContext(HttpWorkerRequest wr); [C++] public: HttpContext(HttpWorkerRequest* wr); [VB] Public Sub New(ByVal wr As HttpWorkerRequest) [JScript] public function HttpContext(wr: HttpWorkerRequest); DETX Description Initializes a new instance of the System.Web.HttpContext class. The System.Web.HttpWorkerRequest object for the current HTTP request. HttpContext Example Syntax: ToString [C#] public HttpContext(HttpRequest request, HttpResponse response); [C++] public: HttpContext(HttpRequest* request, HttpResponse* response); [VB] Public Sub New(ByVal request As HttpRequest, ByVal response As HttpResponse) [JScript] public function HttpContext(request: HttpRequest, response: HttpResponse); Initializes a new instance of the System.Web.HttpContext class. DETX Description Initializes a new instance of the System.Web.HttpContext class. The System.Web.HttpRequest object for the current HTTP request. The System.Web.HttpResponse object for the current HTTP request. AllErrors ToString [C#] public Exception[ ] AllErrors {get;} [C++] public: _property Exception* get_AllErrors( ); [VB] Public ReadOnly Property AllErrors As Exception( ) [JScript] public function get AllErrors( ): Exception[ ]; DETX Description Gets an array of errors accumulated while processing an HTTP request. Application ToString [C#] public HttpApplicationState Application {get;} [C++] public: _property HttpApplicationState* get_Application( ); [VB] Public ReadOnly Property Application As HttpApplicationState [JScript] public function get Application( ): HttpApplicationState; DETX Description Gets the System.Web.HttpApplicationState object for the current HTTP request. ApplicationInstance ToString [C#] public HttpApplication ApplicationInstance {get; set;} [C++] public: _property HttpApplication* get_ApplicationInstance( );public: _property void set_ApplicationInstance(HttpApplication*); [VB] Public Property ApplicationInstance As HttpApplication [JScript] public function get ApplicationInstance( ): HttpApplication;public function set ApplicationInstance(HttpApplication); DETX Description Gets or sets the System.Web.HttpApplicationState object for the current HTTP request. Cache ToString [C#] public Cache Cache {get;} [C++] public: _property Cache* get_Cache( ); [VB] Public ReadOnly Property Cache As Cache [JScript] public function get Cache( ): Cache; DETX Description Gets the System.Web.Caching.Cache object for the current HTTP request. Current ToString [C#] public static HttpContext Current {get;} [C++] public: _property static HttpContext* get_Current( ); [VB] Public Shared ReadOnly Property Current As HttpContext [JScript] public static function get Current( ): HttpContext; DETX Description Gets the System.Web.HttpContext object for the current HTTP request. Error ToString [C#] public Exception Error {get;} [C++] public: _property Exception* get_Error( ); [VB] Public ReadOnly Property Error As Exception [JScript] public function get Error( ): Exception; DETX Description Gets the first error (if any) accumulated during HTTP request processing. Handler ToString [C#] public IHttpHandler Handler {get; set;} [C++] public: _property IHttpHandler* get_Handler( );public: _property void set_Handler(IHttpHandler*); [VB] Public Property Handler As IHttpHandler [JScript] public function get Handler( ): IHttpHandler;public function set Handler(IHttpHandler); DETX Description Gets or sets the System.Web.IHttpHandler object for the current HTTP request. IsCustomErrorEnabled ToString [C#] public bool IsCustomErrorEnabled {get;} [C++] public: _property bool get_IsCustomErrorEnabled( ); [VB] Public ReadOnly Property IsCustomErrorEnabled As Boolean [JScript] public function get IsCustomErrorEnabled( ): Boolean; DETX Description Gets a value indicating whether custom errors are enabled for the current HTTP request. IsDebuggingEnabled ToString [C#] public bool IsDebuggingEnabled {get;} [C++] public: _property bool get_IsDebuggingEnabled( ); [VB] Public ReadOnly Property IsDebuggingEnabled As Boolean [JScript] public function get IsDebuggingEnabled( ): Boolean; DETX Description Gets a value indicating whether the current HTTP request is in debug mode. Items ToString [C#] public IDictionary Items {get;} [C++] public: _property IDictionary* get_Items( ); [VB] Public ReadOnly Property Items As IDictionary [JScript] public function get Items( ): IDictionary; DETX Description Gets a key-value collection that can be used to organize and share data between an System.Web.IHttpModule and an System.Web.IHttpHandler during an HTTP request. Request ToString [C#] public HttpRequest Request {get;} [C++] public: _property HttpRequest* get_Request( ); [VB] Public ReadOnly Property Request As HttpRequest [JScript] public function get Request( ): HttpRequest; DETX Description Gets the System.Web.HttpRequest object for the current HTTP request. Response ToString [C#] public HttpResponse Response {get;} [C++] public: _property HttpResponse* get_Response( ); [VB] Public ReadOnly Property Response As HttpResponse [JScript] public function get Response( ): HttpResponse; DETX Description Gets the System.Web.HttpResponse object for the current HTTP response. Server ToString [C#] public HttpServerUtility Server {get;} [C++] public: _property HttpServerUtility* get_Server( ); [VB] Public ReadOnly Property Server As HttpServerUtility [JScript] public function get Server( ): HttpServerUtility; DETX Description Gets the System.Web.HttpServerUtility object that provides methods used in processing Web requests. Session ToString [C#] public HttpSessionState Session {get;} [C++] public: _property HttpSessionState* get_Session( ); [VB] Public ReadOnly Property Session As HttpSessionState [JScript] public function get Session( ): HttpSessionState; DETX Description Gets the System.Web.SessionState instance for the current HTTP request. SkipAuthorization ToString [C#] public bool SkipAuthorization {get; set;} [C++] public: _property bool get_SkipAuthorization( );public: _property void set_SkipAuthorization(bool); [VB] Public Property SkipAuthorization As Boolean [JScript] public function get SkipAuthorization( ): Boolean;public function set SkipAuthorization(Boolean); DETX Description Gets or sets a value that specifies whether the URLAuthorization module will skip the authorization check for the current request. SkipAuthorization is for advanced use by authentication modules that need to redirect to an anonymous-allowed page. The Forms authentication module and Passport authentication module both set this property when redirecting to a configured login page. Setting this requires the ControlPrincipal flag to be set in System.Security.Permissions.SecurityPermission.Flags. Timestamp ToString [C#] public DateTime Timestamp {get;} [C++] public: _property DateTime get_Timestamp( ); [VB] Public ReadOnly Property Timestamp As DateTime [JScript] public function get Timestamp( ): DateTime; DETX Description Gets the initial timestamp of the current HTTP request. Trace ToString [C#] public TraceContext Trace {get;} [C++] public: _property TraceContext* get_Trace( ); [VB] Public ReadOnly Property Trace As TraceContext [JScript] public function get Trace( ): TraceContext; DETX Description Gets the System.Web.TraceContext object for the current HTTP response. User ToString [C#] public IPrincipal User {get; set;} [C++] public: _property Iprincipal* get_User( );public: _property void set_User(IPrincipal*); [VB] Public Property User As IPrincipal [JScript] public function get User( ): IPrincipal;public function set User(IPrincipal); DETX Description Gets or sets security information for the current HTTP request. Setting this property requires the ControlPrincipal flag to be set in System.Security.Permissions.SecurityPermission.Flags. AddError [C#] public void AddError(Exception errorInfo); [C++] public: void AddError(Exception* errorInfo); [VB] Public Sub AddError(ByVal errorInfo As Exception) [JScript] public function AddError(errorInfo: Exception); DETX Description Adds an exception to the exception collection for the current HTTP request. The System.Exception object to add to the exception collection. ClearError [C#] public void ClearError( ); [C++] public: void ClearError( ); [VB] Public Sub ClearError( ) [JScript] public function ClearError( ); DETX Description Clears all errors for the current HTTP request. GetAppConfig [C#] public static object GetAppConfig(string name); [C++] public: static Object* GetAppConfig(String* name); [VB] Public Shared Function GetAppConfig(ByVal name As String) As Object [JScript] public static function GetAppConfig(name: String): Object; DETX Description Returns requested configuration information for the current application The application configuration tag that information is requested for. GetConfig [C#] public object GetConfig(string name); [C++] public: Object* GetConfig(String* name); [VB] Public Function GetConfig(ByVal name As String) As Object [JScript] public function GetConfig(name: String): Object; Returns requested configuration information for the current HTTP request. DETX Description Returns requested configuration information for the current HTTP request. The configuration tag that information is requested for. RewritePath [C#] public void RewritePath(string path); [C++] public: void RewritePath(String* path); [VB] Public Sub RewritePath(ByVal path As String) [JScript] public function RewritePath(path: String); DETX Description Assigns an internal rewrite path. The internal rewrite path. IServiceProvider.GetService [C#] object IServiceProvider.GetService(Type service); [C++] Object* IServiceProvider::GetService(Type* service); [VB] Function GetService(ByVal service As Type) As Object Implements IServiceProvider.GetService [JScript] function IServiceProvider.GetService(service: Type): Object; HttpCookie class (System.Web) ToString DETX Description Provides a type-safe way to create and manipulate individual HTTP cookies. The System.Web.HttpCookie class gets and sets properties of individual cookies. The System.Web.HttpCookieCollection class provides methods to store, retrieve, and manage all the cookies for an entire Web application. ASP.NET code uses the intrinsic System.Web.HttpResponse.Cookies object to create cookies and add them to the cookie collection. When delivering a Web page to a client, the server sends the entire cookie collection with the Set-Cookie header. HttpCookie Example Syntax: ToString [C#] public HttpCookie(string name); [C++] public: HttpCookie(String* name); [VB] Public Sub New(ByVal name As String) [JScript] public function HttpCookie(name: String); Initializes a new instance of the System.Web.HttpCookie class. DETX Description Creates and names a new cookie. The name of the new cookie. HttpCookie Example Syntax: ToString [C#] public HttpCookie(string name, string value); [C++] public: HttpCookie(String* name, String* value); [VB] Public Sub New(ByVal name As String, ByVal value As String) [JScript] public function HttpCookie(name: String, value: String); DETX Description Creates, names, and assigns a value to a new cookie. The name of the new cookie. The value of the new cookie. Domain ToString [C#] public string Domain {get; set;} [C++] public: _property String* get_Domain( );public: _property void set_Domain(String*); [VB] Public Property Domain As String [JScript] public function get Domain( ): String;public function set Domain(String); DETX Description Gets or sets the domain to associate the cookie with. Setting the Domain attribute limits transmission of the cookie to clients requesting a resource from that domain. Expires ToString [C#] public DateTime Expires {get; set;} [C++] public: _property DateTime get_Expires( );public: _property void set_Expires(DateTime); [VB] Public Property Expires As DateTime [JScript] public function get Expires( ): DateTime;public function set Expires(DateTime); DETX Description Gets or sets the expiration date and time for the cookie. HasKeys ToString [C#] public bool HasKeys {get;} [C++] public: _property bool get_HasKeys( ); [VB] Public ReadOnly Property HasKeys As Boolean [JScript] public function get HasKeys( ): Boolean; DETX Description Gets a value indicating whether a cookie has subkeys. Item ToString [C#] public string this[string key] {get; set;} [C++] public: _property String* get_Item(String* key);public: _property void set_Item(String* key, String*); [VB] Public Default Property Item(ByVal key As String) As String [JScript] returnValue=HttpCookieObject.Item(key);HttpCookieObject.Item(key- )=returnValue; DETX Description Shortcut for HttpCookie.Values[key]. This property is provided for compatibility with previous versions of ASP. Key (index) of cookie value. Name ToString [C#] public string Name {get; set;} [C++] public: _property String* get_Name( );public: _property void set_Name(String*); [VB] Public Property Name As String [JScript] public function get Name( ): String;public function set Name(String); DETX Description Gets or sets the name of a cookie. Path ToString [C#] public string Path {get; set;} [C++] public: _property String* get_Path( );public: _property void set_Path(String*); [VB] Public Property Path As String [JScript] public function get Path( ): String;public function set Path(String); DETX Description Gets or sets the virtual path to transmit with the current cookie. The Path property extends the Domain property to completely describe the specific URL that the cookie applies to. For example, in the URL http:/www.microsoft.com/asp, the domain is www.microsoft.com and the path is /asp. Secure ToString [C#] public bool Secure {get; set;} [C++] public: _property bool get_Secure( );public: _property void set_Secure(bool); [VB] Public Property Secure As Boolean [JScript] public function get Secure( ): Boolean;public function set Secure(Boolean); DETX Description Gets or sets a value indicating whether to transmit the cookie securely (that is, over HTTPS only). Value ToString [C#] public string Value {get; set;} [C++] public: _property String* get_Value( );public: _property void set_Value(String*); [VB] Public Property Value As String [JScript] public function get Value( ): String;public function set Value(String); DETX Description Gets or sets an individual cookie value. Values ToString [C#] public NameValueCo