Originally installed on the reporting service is also a bit mysterious, after all, before doing this project has not really contacted the Microsoft to replace the Crystal Report tool, and Microsoft does not seem to be satisfied with a report tool so simple.
Reporting Services is a new server-based reporting platform that is deployed on a microsoft®sql server™2000 basis to create and manage tabular reports, matrix reports, and data from relational data sources and multidimensional data sources. Graphical reports and Free-form reports. You can view and manage reports that you create through a web-based connection.
Reporting Services provides a complete set of service, tools, and application programming interfaces (APIs) that you can use Reporting services even if you are not a programmer. You can use the applications and tools included in Reporting Services to produce, publish, and manage reports. In addition, tools or applications that support various stages of the reporting lifecycle are provided. Programmers can use APIs to extend or integrate report functionality into a custom solution.
This article mainly introduces some of the technologies involved in the development of reporting Service, first of all we can know from it is a service, it provides a Web service interface, and allows us to embed code in the report (Must be VB. NET), you can also reference assemblies based on the. NET Framework.
This is mainly about two aspects of reporting service development related technology
1. Integrating the Reporting Services provided by the reporting service in a custom application
To generate a report presentation component
To integrate the Reporting Service report (RDL file) into a custom application, we can display the component from a reporting service with a report that can be compiled from the sample project ReportViewer Default is ReportViewer.dll.
By compiling the sample project ReportViewer, we can get the components that are used to integrate the RDL file in the custom application, but if we need to pass parameters to the report in a custom application, the ReportViewer.dll component that is compiled with the default is not supported. Next, we're going to solve this problem, how do we assign a value to a report parameter in a custom application?
Copy Code code as follows:
private void Setparameter (string name, String value)
{
...
...
}
The effect of this method would be to set a value for the report parameter, and you might be happy because it provides a way to support it, but when we see private, we may not be happy, Microsoft Basic Security considerations, the default state does not pass the parameters of the method exposed. But often the implementation of application and security are mutually exclusive.
Now we know at least how to extend the functionality to achieve our goals.
Copy Code code as follows:
public void Setqueryparameter (string Name, String value)
{
This. Setparameter (Name, value);
}
We add a public approach to setqueryparameter. Again, this component has the function of parameter transfer.
