You will need to specify a folder location for your project, as well as a Web access method. If you select the FrontPage method, you must have the FrontPage Extensions installed and configured on the server where you want to deploy your Report Web Service. Choose the File share method if you have direct access to the server and just want to copy the files over.
At the bottom of the dialog, you will also need to select what files you want copied across to the Web server. You have three choices:
□ Copy files needed to run this application—will copy across all of the built output files and any files where the BuildAction property is set to Content
□ All project files—will copy across everything, including the output and source files, and so on
□ All files in the source project folder—will copy across all files within the folder, regardless of whether they are included in the project
The second method of deploying a Report Web Service involves creating a Web setup project that can be used to deploy your service on a local or remote Web server. To create a new Web setup project, select New ^ Project and from the folder marked Setup and Deployment Projects, select the icon for Web Setup Project and make sure you click the radio button for Add to Solution (instead of Close Solution).
A new tab called File System on Target Machine will open. Right-click the Web Application Folder and select Add ^ Project Output. From the dialog that appears, shown in Figure 6-14, select Content Files, Primary Output, and Debug Symbols all at once using Ctrl-click.
With these components added, save your project and select Build WebServiceSetup to create a Windows Installer Package (MSI) that will install your Report Web Service. If you are deploying this to a server that does not have Visual Studio .NET or the .NET Framework installed, you will need to install that before you install and deploy your Report Web Service.
Was this article helpful?