ActiveReports 14
ActiveReports 14 User Guide / How To / Localize and Deploy / Deploy Web Applications
In This Topic
    Deploy Web Applications
    In This Topic

    Follow this guide to deploy ActiveReports Web projects to your Web server. For Web projects using the Professional Edition HttpHandlers, see Configure HTTPHandlers in IIS 8 and IIS 10.

    Before you begin

    To deploy ActiveReports Web projects, you must have access to the Microsoft .NET Framework version 4.6.2 or higher and the coordinating version of ASP.NET, or ASP.NET Core with .NET Core 2.1 and above. You must also have access to Internet Information Services version 8 or higher, and you need administrative access to the server.

    It is also good to be sure that all of the references you need for your reports are included. Here is a table listing features and required DLLs.

    Features and References

    These assemblies are added automatically when you add controls to forms or report controls to code-based section reports, but Visual Studio does not do this with XML-based (RPX and RDLX) reports.

    Feature Required Package
    Export: Excel

    GrapeCity.ActiveReports.Export.Excel
    GrapeCity.ActiveReports.Core.Export.Excel.Page

    Export: HTML GrapeCity.ActiveReports.Export.Html
    GrapeCity.ActiveReports.Core.Export.Html.Page
    Export: Image GrapeCity.ActiveReports.Export.Image
    GrapeCity.ActiveReports.Core.Export.Image.Page
    Export: PDF GrapeCity.ActiveReports.Export.Pdf
    GrapeCity.ActiveReports.Core.Export.Pdf.Page
    Export: Word/RTF

    GrapeCity.ActiveReports.Export.Word.dll                        

    Export: XML GrapeCity.ActiveReports.Export.Xml
    Export: CSV/JSON GrapeCity.ActiveReports.Core.Export.Text.Page              
    WebViewer or HttpHandlers (Pro Edition only)

    GrapeCity.ActiveReports.Web
    Grapecity.ActiveReports.Web.Viewer

    JS Viewer GrapeCity.ActiveReports.Aspnetcore.Viewer
    GrapeCity.ActiveReports.Aspnet.Viewer              
    Web Designer GrapeCity.ActiveReports.Aspnetcore.Designer
    GrapeCity.ActiveReports.Aspnet.Designer

    Other packages that are required for deploying web applications are as follows:
    • GrapeCity.ActiveReports
    • GrapeCity.ActiveReports.Core.Rdl        
    • Newtonsoft.Json
    • Gcef.Data.DataEngine
    • Gcef.Data.VBFunctionLib
    • Gcef.Data.ExpressionInfo
    • Grapecity.DataVisualization
    • GrapeCity.ActiveReports.Core.Rendering
    • GrapeCity.ActiveReports.Core.Drawing.Gdi
    • GrapeCity.ActiveReports.Core.DataProviders
    • GrapeCity.ActiveReports.Chart
    • GrapeCity.ActiveReports.Document

    To install prerequisites on the server

    Follow Microsoft's instructions to install each of the following on your Web server:

    • The Microsoft .NET Framework version 4.6.2 or higher
    • ASP.NET version 4.6.2 or higher (must be the same version as the Framework)
    • ASP.NET Core with .NET Core 2.1 and above.
    • Internet Information Services (IIS) version 8

    To map your application to a virtual directory

    1. Make sure your project is deployed to a virtual directory in IIS.
    2. To map requests from the page with the WebViewer control to your virtual directory, paste the <base> tag with a virtual directory name inside the <head> tag of the page containing the WebViewer control. In this case, all requests to backend assemblies will include the specified virtual directory name. For example,

      <head>
       <base href="/VirtDirName/">
      </head>

    To set permissions on the server

    Depending on your project, you may need to set permissions to allow ActiveReports access to data or folders.

    Some examples of required permissions on the server:

    • If you are saving files (e.g. PDF or RDF exports) to a folder on Windows machines, the ASPNET user ID needs Write access to that folder.
    • Windows is user configurable, so use the name assigned to the ASPNET user instead.
    • If your application reads anything from any folder, assign Read access to it.
    • If your reports run on any networked data source (e.g. SQL, Access, etc.) assign Read access to it.
    • If you use CacheToDisk, assign IsolatedStorageFilePermission to it.
    See Also