This documentation is archived and is not being maintained.

Reports as Web Services

Visual Studio .NET 2003

You can publish a report as a Web Service. A Report Web Service can be accessed by any application — Windows or Web — that uses the appropriate viewer.

When you create a Crystal report in a project (or add an existing Crystal report to a Web Service project) and generate a Report Web Service, Visual Studio compiles the Web Service to a dll and generates an Extensible Markup Language (XML) file that describes the public functions, input parameters, data types, and return data types exposed by the Report Web Service. Both the dll and the XML files are published on the Web server as a Report Web Service. A client on a Web browser invokes the Report Web Service via HTTP, and XML is used to pass data to and from the Web Service.

Once the Report Web Service has been published on a Web server, it can be consumed by an application on the client side. You can add the Report Web Service from the Visual Studio Server Explorer to a Windows application, an ASP.NET Web application or a Managed C++ application. This action has the same outcome as invoking the Report Web Service on a browser. A Web Service Description Language (.wsdl) file is automatically generated on the client.

In order for the Report Web Service to be used by another application, you need to follow these key tasks:

Key Task Options Available
Create the Report Web Service. Creating the Report Web Service with an existing report.
Create an application to consume the Report Web Service.

This application must contain a Crystal Report Viewer.

Adding Web Forms Viewers to Applications.

Adding Windows Forms Viewers to Applications.

Connecting to Report Web Services on a Client

Bind the Report Web Service to the viewer. Report Web Service Binding Options for Web Form Viewers.

Report Web Service Binding Options for Windows Forms Viewers.

Build and run the application. Building and Running Web Applications.

Building and Running Windows Applications.

See Also

Reporting Deployment Scenarios