ASP.NET Browser Registration Tool (Aspnet_regbrowsers.exe)

The ASP.NET Browser Registration tool (Asnet_regbrowsers.exe) parses and compiles all system-wide browser definitions into an assembly and installs the assembly into the global assembly cache. The tool uses the browser definition files (.BROWSER files) from the .NET Framework Browsers subdirectory.

Syntax

aspnet_regbrowsers.exe <options>

Options

Remarks

Browser definition files can be either system-wide or application-specific, and each type is stored in a different location. System-wide browser definition files are stored in the following path:

%SystemRoot%\Microsoft.NET\Framework\version\CONFIG\Browsers

This directory contains predefined browser definition files that shipped with the corresponding version of the .NET Framework, and any additional browser definition files copied there from software updates or service packs. You can add new browser files for browser definitions that you want to be globally available to Web applications. However, do not change the predefined browser definition files that come with ASP.NET, because service packs might update those files and overwrite your changes.

Application-specific browser definition files can be placed in the application's App_Browsers directory. Using the ASP.NET Browser Registration tool has no effect on application-specific browser definition files stored in an application's App_Browsers directory.

When browser definition files at the system level are modified, they do not automatically cause an update of browser capabilities for all applications. You must run the ASP.NET Browser Registration tool to update the browser capabilities assembly.

The ASP.NET Browser Registration tool parses and compiles all system-wide browser definitions into an assembly and installs the assembly in the global assembly cache. If there are errors in the system-wide browser definitions, the tool reports those errors. The browser capabilities assembly is used by all Web applications on the system. Note that you can also programmatically recompile system-wide browser definition files by using the BrowserCapabilitiesCodeGenerator class.

Behavior

When the ASP.NET Browser Registration tool runs, a new assembly is created and the effect on all Web applications is the same as if the Machine.config file was changed: All running Web applications are recycled and Microsoft Internet Information Services (IIS) is restarted. The tool also generates a random private token file, and creates a key file to sign the assembly so the assembly can be installed in the global assembly cache. The key file is removed when the tool is finished, leaving only the public key.

At run time, browser definition information is merged into a collection of known browsers in a BrowserCapabilitiesFactory object. When a request is made, ASP.NET identifies the requesting browser by the request header, and compiles an HttpBrowserCapabilities object that corresponds to the type of the requested browser.

Browser definition files at the application level are parsed and compiled with the other application source files. For a Web site project, compilation happens on demand when the application is started, and the application is automatically recompiled when any changes are made to the application's Browsers directory. The ASP.NET Browser Registration tool has no effect on application-level browser information files.

Examples

To parse and compile all system-wide browser definitions into an assembly and install the assembly into the global assembly cache, run the following command:

aspnet_ regbrowsers.exe -i

You can also use the tool to remove the browser definition assembly from the global assembly cache. The following command removes the browser definitions assembly from the global assembly cache:

aspnet_ regbrowsers.exe -u

To get help on using the ASP.NET Browser Registration tool, use the following command:

aspnet_ regbrowsers.exe -?

Finding the Correct Version of Aspnet_regbrowsers.exe

Aspnet_regbrowsers.exe is installed in the Microsoft.NET Framework directory. If the computer is running multiple .NET Framework versions side-by-side, multiple versions of the tool might be installed. The following table lists the locations where the tool is installed for different versions of the .NET Framework.

See Also

Tasks

How to: Detect Browser Types and Browser Capabilities in ASP.NET Web Forms

Reference

BrowserCapabilitiesFactory

Browser

HttpCapabilitiesBase

Browser Definition File Schema (browsers Element)

Concepts

ASP.NET Web Server Controls and Browser Capabilities

Securing Browser Definition Files