R – asp.net web reference for reporting services

asp.netreporting-servicesweb services

I'm trying to access a reporting services site using the provided web services, from a basic asp.net website.

I've added the reference to reportservice2005.asmx on the reporting server, but I'm having problems getting intellisense working and for anything to run/compile.

From examples, I've seen people create an instance of the service with the following: "ReportingService rService = new ReportingService();" – where ReportingService is the name of the web reference, created in visual studio. I've amended this to vb.net code but get errors.. it's as if ReportingService is the namespace and I need to choose one of the classes inside.

So I tried "dim rService as ReportingService.ReportingService2005"

Is this correct? it seems to work with intellisense, however when I then try to run the code, I get the compilation error: "Type 'ReportingService.ReportingService2005' is not defined."

Any ideas?
Cheers! 😀

Best Answer

While adding the web reference you surely asked to enter the reference name.. first import the reference into your class file. And try creating the instacnes.. this should work..

Included Sample Code

using WindowsApplication1.ConfigWS;

ConfigWS is the webreference name i have created. And it has to imported to the project and it must be prefixed with current namespace name (if available).

check the below sample code used to instantiate the webmethod (CreateServer) defined in ConfigWS webservice.

private void Form1_Load(object sender, EventArgs e)
{
        WindowsApplication1.ConfigWS.CConfigurationManagerBCWS objWs = new CConfigurationManagerBCWS();
        CReqMsgCreateServer objCreateServer=new CReqMsgCreateServer();
        objCreateServer.objServerConfig =new CServerConfig();
        objCreateServer.objServerConfig.ServerName="****";
        objCreateServer.objServerConfigVOBC.LevelFlag ="---";
        CResMsgCreateServer objRes = objWs.CreateServer(objCreateServer);    
}

Website:

The Web Site project is compiled on the fly. You end up with a lot more DLL files, which can be a pain. It also gives problems when you have pages or controls in one directory that need to reference pages and controls in another directory since the other directory may not be compiled into the code yet. Another problem can be in publishing.

If Visual Studio isn't told to re-use the same names constantly, it will come up with new names for the DLL files generated by pages all the time. That can lead to having several close copies of DLL files containing the same class name, which will generate plenty of errors. The Web Site project was introduced with Visual Studio 2005, but it has turned out not to be popular.

Web Application:

The Web Application Project was created as an add-in and now exists as part of SP 1 for Visual Studio 2005. The main differences are the Web Application Project was designed to work similarly to the Web projects that shipped with Visual Studio 2003. It will compile the application into a single DLL file at build time. To update the project, it must be recompiled and the DLL file published for changes to occur.

Another nice feature of the Web Application project is it's much easier to exclude files from the project view. In the Web Site project, each file that you exclude is renamed with an excluded keyword in the filename. In the Web Application Project, the project just keeps track of which files to include/exclude from the project view without renaming them, making things much tidier.

Reference

The article ASP.NET 2.0 - Web Site vs Web Application project also gives reasons on why to use one and not the other. Here is an excerpt of it:

You need to migrate large Visual Studio .NET 2003 applications to VS 2005? use the Web Application project.

You want to open and edit any directory as a Web project without creating a project file? use Web Site project.

You need to add pre-build and post-build steps during compilation? use Web Application project.

You need to build a Web application using multiple Web projects? use the Web Application project.

You want to generate one assembly for each page? use the Web Site project.

You prefer dynamic compilation and working on pages without building entire site on each page view? use Web Site project.

You prefer single-page code model to code-behind model? use Web Site project.

Web Application Projects versus Web Site Projects (MSDN) explains the differences between the web site and web application projects. Also, it discusses the configuration to be made in Visual Studio.

C# – How to display a Reporting Services report as an inline PDF, in a ASP.Net and C# web page

I'm doing something that is very similar. But I'm using a HttpWebRequest instead of using the service. Here's how I'm doing it. The important part is the inline before the file name in the Content-Disposition.

It also depends on their version of Adobe Reader (we found they need 7 or upwards) and the settings they have set inside it (in case they've set it to not open PDFs inside the browser).

HttpResponse currentResponse = HttpContext.Current.Response;
currentResponse.Clear();
currentResponse.ClearHeaders();
currentResponse.ClearContent();

filename = String.Format("{0}.pdf", this.ReportName);
currentResponse.AppendHeader("Content-Disposition", String.Format("inline;filename={0}", filename));
currentResponse.ContentType = "Application/PDF";

//Copy the content of the response to the 
//current response using BinaryWrite
snip....

currentResponse.End();

Best Answer

Related Solutions

.net – ASP.NET Web Site or ASP.NET Web Application

Website:

Web Application:

C# – How to display a Reporting Services report as an inline PDF, in a ASP.Net and C# web page

Related Topic