Re-release the ReportViewer Control

The redistributable reportviewer control is a self-decompressed file named reportviewer.exe, which includes a. MSI file and other files. You can find reportviewer.exe: % ProgramFiles % \ microsoft sdks \ windows \ v7.0a \ bootstrapper \ packages \ reportviewer \ reportviewer.exe in the following locations. You can also download it from the Microsoft download center.

Note:
Different versions of the redistributable ReportViewer control can be installed on the same computer.

When you run reportviewer.exe, the following files are installed in the Global Assembly Cache folder on the computer where the application is deployed.

• Microsoft. ReportViewer. Common. dll

• Microsoft. ReportViewer. ProcessingObjectModel. dll

• Microsoft. ReportViewer. WebForms. dll

• Microsoft. ReportViewer. WinForms. dll

• Microsoft. ReportViewer. DataVisualization. dll

Run reportviewer.exe

The type of the control you use determines the location where reportviewer.exe is run.

• For ASP. NET applications, ReportViewer.exe should be run on the Web server that hosts the application. This operation must be performed by the server administrator.

• For Windows Forms applications, controls should be included as essential components of the application system so that they are automatically installed along with the application. You can use the bootstrap application to automatically complete this step:

  1. Open the project properties page.

  2. Click"Publish"And then click"System essential".

  3. Select"Microsoft Visual Studio 2010 report viewer"And then click"OK".

  4. Publish an application.

When installing the application, the system checks the local computer to see if reportviewer is installed. If not, the installer will install it.

Deploy the localized version of The reportviewer Control

The release of the reportviewer control is now available in 10 Visual Studio languages: Simplified Chinese, traditional Chinese, French, German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish. If you want to install the localized version of Visual Studio, you can go to % ProgramFiles % \ microsoft sdks \ windows \ v7.0a \ bootstrapper \ packages \ reportviewer \ <Lang> Find the localized redistributable reportviewer control. You can also download any localized re-release reportviewer from the web.

To use the releaseable reportviewer control of the localized version that comes with Visual Studio, perform the following operations:

1. Run ReportViewer.exe.

2. Locate the folder that contains the Language Pack to use. The Language Pack folder is located in % PROGRAMFILES % \ Microsoft SDKs \ Windows \ v7.0A \ BootStrapper \ Packages \ ReportViewer \ <Lang>.

3. Run ReportViewerLP.exe.

To"ReportViewer"You can use Microsoft. Reporting. WebForms. IreportViewerMessages3 or Microsoft. Reporting. WinForms. IreportViewerMessages3 to create tooltip and other user interface text in a specific language.

Determine the browser Language and Culture settings

When using the ReportViewer Web Server Control to host reports in browser applications, if you want to provide a user interface that matches the browser Language and Culture settings, you must set the thread culture. ASP. NET does not set the thread culture based on the header information provided by the client. To make the application match the browser's regional settings, you can set System. Threading. Thread. CurrentCulture and System. Threading. Thread. CurrentUICulture in the application code. For more information about how to handle the application's regional settings, see System. Globalization. CultureInfo.

Precautions for deploying the Web server control of the report Viewer

Other configurations are required for deploying ASP. NET applications in the Web farm to ensure that the view status is maintained throughout the farm. If you deploy the ReportViewer Web Server Control in the Web environment, specifyMachineKeyElement. For more information, see ReportViewer's Web. config settings.

Reports processed in the ReportViewer Web Server Control have different browser requirements. Browser compatibility issues may affect the availability of some types of report functions. For more information, see browser support for the ReportViewer Web Server Control.

Distribute report files

Unless you useLocalReport. LoadReportDefinitionOrServerReport. LoadReportDefinitionThe method dynamically generates client report definitions at runtime. Otherwise, there are several different options for distributing report files together with the application, depending on the processing mode of the report viewer control.

Locally processed reports can be stored in network folders or compiled into executable applications. Reports processed on remote servers are usually stored on the SQL Server Reporting Services Report Server. Unless you want to useServerReport. LoadReportDefinitionMethod to manually load a report from a location other than the Report Server; otherwise, no report files to be included in the application. To deploy a report published on the Report Server, you must have the permission to access the Report Server and ensure that the application user has the right to view the reports on the server. To deploy a server report, you must understand the identity authentication extensions used by the Report Server, as well as the role-based authentication mode that provides content access and operation permissions. For more information, see precautions for deploying server reports.