Assists in reading in the <browserCaps> section of a configuration file and creating an instance of the HttpBrowserCapabilities class that contains the capabilities information for the client browser.
Assembly: System.Web (in System.Web.dll)
Thetype exposes the following members.
|Create||Creates an instance of the HttpBrowserCapabilities class that contains the capabilities information for the client browser.|
|Equals(Object)||Determines whether the specified object is equal to the current object. (Inherited from Object.)|
|Finalize||Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)|
|GetHashCode||Serves as the default hash function. (Inherited from Object.)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|ToString||Returns a string that represents the current object. (Inherited from Object.)|
The class and the corresponding <browserCaps> configuration section have been deprecated in the .NET Framework version 2.0. The preferred method for managing browser capabilities is through browser definition files that are compiled for use by the BrowserCapabilitiesFactory class. The goal of both configuration methodologies is to generate an instance of the HttpBrowserCapabilities class that can be accessed from the Browser property of the HttpRequest class.
Using the browser definition files to store browser capabilities affords advantages over the alternative. It offers improved performance because the browser definition information is parsed from the XML configuration file and compiled into a class ahead of time. The browser definition files are also easier to maintain:
The definitions are hierarchical, and thus rely less on regular expressions to determine the browser capabilities.
The definitions can be organized in multiple files, making them easier to manage.
The definitions can be defined at any level, either at the Machine.config level or a specific application level. This eliminates the need to copy the entire set of definitions for the purpose of overriding the capabilities for a specific browser.