Reputation: 13561
I have a report that was not displaying, thanks to ASP.NET Report Viewer runs but doesn't show any data, I was able to get it to work (adding AsyncPostBackTimeout to the script manager tag), but there's still one last lingering problem:
If the web.config has <compilation debug="false" targetFramework="4.8">
it still doesn't display. I can change that to <compilation debug="true" targetFramework="4.8">
and my problematic report views just fine. Unlike the accepted answer in ReportViewer control not displaying reports, I set AsyncRendering to true, but setting it to false doesn't help. One problem I have is that when ran locally, it works. I'm using Microsoft.ReportViewer.WebForms, Version=15.0.0.0, PublicKeyToken=89845DCD8080CC91 in the config and pulling it in using the latest nuget package.
So, two questions: any solution to the problem, and any explanation as to why setting debug changes the behavior?
<%@ Page Language="C#" AutoEventWireup="true"
EnableEventValidation="false"
CodeBehind="Example.aspx.cx"
Inherits="Example" %>
...
<asp:ScriptManager ID="ScriptManager1" AsyncPostBackTimeout="0" runat="server" />
<rv:ReportViewer ID="rv1" ProcessingMode="Remote"
OnBack="rv1_Back" OnDrillthrough="rv1_Drillthrough"
AsyncRendering="false" BackColor="#ECE9D8" Height="100%" Width="100%" Visible="false" runat="server" >
</rv:ReportViewer>
Upvotes: 0
Views: 12