ReportViewer shows a blank window

[Manfred]

Hi,

after resolving the problem with the initialization Xaml-Parse error I added the binding redirects into my app.config.
Now the window with the report opens, but it shows only a blank window without the Control.

Any hints?
I am using the newest versions of reporting and WPF.

Best regards
Manfred

[Greg]

I've got the same/similar problem. My app has been in production for a year. I updated to the latest UI for WPF and Reporting and now when my app opens the report viewer I get nothing. No compile errors. No runtime errors. The ReportViewer just doesn't render.

I've added binding redirects to the app.config, made sure all of the projects reference the right DLL's, and my application code hasn't changed at all.

What gives, Telerik?

[Stef]

Hi,

Below is quote from my reply in a support ticket opened on behalf of Manfred:

"For each major Q release usually the WPF ReportViewer is built against the corresponding major Q version of Telerik UI for WPF, unless there are special circumstances causing us to use other fully tested version.

In the current Q1 2014 release we have used the latest UI for WPF release for Q3 2013, thus you need to add binding redirects to the greater version of the assemblies. For more details check How to: Add report viewer to a WPF application article.

Also as of Q1 2014 the WPF ReportViewer uses implicit styles, thus you need to use the WPF NoXAML binaries and add the XAML files and related resources additionally. For more details check the Setting a Theme (Using Implicit Styles) article and our local demos, installed by default under C:\Program Files (x86)\Telerik\Reporting Q1 2014\Examples."

Note that if you upgrade the UI for WPF assemblies, you need to upgrade their XAML files as well. The only XAMl file you need to copy from Telerik Reporting product folder is Telerik.ReportViewer.Wpf.xaml.

Regards,
Stef
Telerik

[Scott]

I waste so many hours on this!  Again, I upgraded my WPF controls and reports to 2014 and again my app doesn't work.  I have updated the bindings to the latest windows controls as I was told last time I did this.  I get blank windows where my reports should be.  Same as the above poster.  I don't understand the stuff about themes, I don't use any themes.   I'm so sorry I hit the upgrade button again!!  When will I learn.

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Windows.Controls" culture="neutral" publicKeyToken="5803cfa389c90ce7"/>
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="2014.1.224.40"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Windows.Controls.Input" culture="neutral" publicKeyToken="5803cfa389c90ce7"/>
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="2014.1.224.40"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Windows.Controls.Navigation" culture="neutral" publicKeyToken="5803cfa389c90ce7"/>
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="2014.1.224.40"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Windows.Controls.GridView" culture="neutral" publicKeyToken="5803cfa389c90ce7"/>
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="2014.1.224.40"/>
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

[Nasko]

Hello Scott,

We have replied to your inquiry about this issue in another forum thread where you have posted. Please check the reply here: WPF Upgrading, I don't see the reportviewer in my vs designer tab.

For more details regarding the WPF Report Viewer showing a blank window please follow the The WPF/Silverlight report viewer is blank after upgrading from version prior to Q1 2014 to Q1 2014 or later KB article.

Regards,
Nasko
Telerik

 

 

[Bob]

I have to agree with Scott,

Every time we upgrade to a new version of reporting it blows up!  This
time we upgraded to VS2013, .net 4.5.1, and Q2 reporting. All seemed to be good
(including the reports) so I rolled it out. Today I was working on a new report
and had to publish out a quick change. No one was going to see the report so It
wasn't a problem. After publishing out the change I get calls that the reports
(which are a large portion of the UI) are blank. I had to roll back to Q3 2012
and of course that version can't work using .net 4.5.1 it only works using .net
4.0.  Is it just me? Why oh why didn't I take the blue pill!
Bob

[Stef]

Hello Bob,

We agree it is not pleasant to have to rewrite portions of long existing projects, but the changes come from the constant work on the reporting engine and the improvements we make to add new features and extend old ones.
To ease the process we aim to provide Upgrade Wizards that handle the upgrade process where possible, and leave minimum manual settings, required by the differences that may exist in different projects and scenarios, which do not allow an automation of the process.
We also started recording in our online help in details changes and dependencies, which are important on upgrade.
Thus our recommendation is to check the release notes and the corresponding help article for changes in the reporting engine before proceeding with the upgrade.

Regards,
Stef
Telerik