I have an asp.net core web app that works fine running from VS 2019 and IIS Express. However, if I run it under a docker windows container, there's an error when deserializing the xml .trxd file.

Exception thrown: 'System.TypeInitializationException' in Telerik.Reporting.dll
Exception thrown: 'System.Reflection.TargetInvocationException' in System.Private.CoreLib.dll
Exception thrown: 'System.Reflection.TargetInvocationException' in System.Private.CoreLib.dll
Exception thrown: 'System.MissingMethodException' in Telerik.Reporting.dll

This is only happening when running in a windows docker container.

Please do some testing with this configuration.

Would like my custom report resolver to implement async calls, so need

public async Task<ReportSource>Resolve(stringreport) supported in IReportResolver
 
Thanks!
 
  

New development is being done with net core 3.1 and netstandard 2.1 and we can no longer create reports in the Report Designer using the ObjectDataSource.

Seems like it's time to update the standalone Report Designer for these new standards.

The following exception occurs when you attempt to add a Html5 Report Viewer from the VS item template in a project that already contains a CLR report:

"Error: Fail to add project reference System.Runtime.InteropServices.COMException (0x80004005): Adding 'WebApplication2' as a project-to-project reference would cause this project to reference itself. at VSLangProj.References.AddProject(Project pProject) at Telerik.Reporting.Vs.Common.ProjectManager.TryAddProjectReference(Project projectToReference)"

The viewer is still added successfully and displays the report.

Hi

If I run the angular report viewer within my main page, all is well. However if the report viewer is hosted in a <p-dialog> (or <p-overlaypanel>), the report does not render (even though data is loaded and the report can be exported). To confirm this, I even have the report visible in a <tr-viewer> on the main page behind the dialog and load them at the same time.

If the dialog is not visible when the main page opens, then the report viewer toolbar is in a column on the left, and is not operational. (see attached)

If the dialog is visible when the main page opens, then the toolbar appears at the top and functions normally. (see attached)

<tr-viewer #rptViewerBody
     [containerStyle]="viewerContainerStyle"
     [serviceUrl]="reportServerUrl"
     [viewMode]="'INTERACTIVE'"
     [scaleMode]="'SPECIFIC'"
     [scale]="1.0">
</tr-viewer>

vs

<p-dialog modal="true"
          appendTo="body" 
          header="Report"
          [(visible)]="showReport"
          [width]="1500" 
          [height]="1500">

        <tr-viewer #rptViewerDialog
            [containerStyle]="viewerContainerStyle"
            [serviceUrl]="reportServerUrl"
            [viewMode]="'INTERACTIVE'"
            [scaleMode]="'SPECIFIC'"
            [scale]="1.0">
        </tr-viewer>
</p-dialog>

In the code, I tried both of these container styles. The result for the dialog was that relative position rendered the toolbar (top or left), but absolute position rendered nothing at all (height became 0)

this.viewerContainerStyle = {
      position: 'absolute',
      top: '0px',
      left: '0px',
      right: '0px',
      bottom: '0px',
      ['font-family']: 'ms sans serif'
    };
this.viewerContainerStyle = {
      position: 'relative',
      width: '1300px',
      height: '1300px',
      ['font-family']: 'ms sans serif'
};

using @progress/telerik-angular-report-viewer": "7.19.718"

Thanks.

Print functionality doesn't work in React application.

Steps to reproduce:

1. You may use the sample project from How to use HTML5 Report Viewer in React Application article.

2. Run the project and click on Print.

The following error can be seen in the browser's console: Resource interpreted as Document but transferred with MIME type application/pdf: "https://demos.telerik.com/reporting/api/reports/clients/a7fdd020ec4/instances/3f53abd1614/documents/c3923e685e6d6ebefb3d11?response-content-disposition=inline".

Currently the Web Report Designer (WRD) can only work with reports stored on the server where the WRD Web API service is hosted.

A nice addition would be the option to select a local TRDX/TRDP file from the client file system and upload it to the server, when opening a new report for edit.
When saving such report there should be an option to download it to the client's file system as well.

With this approach the open/save operations will more closely resemble those of the standalone report designer.

Under Linux, when the font is set with Conditional Formatting some of the TextBoxes may be rendered with different that the expected Font in Docx. Other TextBoxes set with the same rule to the same font are rendered correctly.

The same report rendered in Docx under Windows produces the correct document.