WPF Upgrading, I don't see the reportviewer in my vs designer tab

9 posts, 2 answers
  1. danparker276
    danparker276 avatar
    389 posts
    Member since:
    Aug 2010

    Posted 03 Mar 2014 Link to this post

    I'm upgrading my reports and on my WPF viewer, it's just blank on the vs design view.  It's also blank when I run it.  
    Just a big blank screen now
    The telerik demos look ok though.  I made sure all the references were the same too.  Probably something very simple I'm missing.
  2. danparker276
    danparker276 avatar
    389 posts
    Member since:
    Aug 2010

    Posted 04 Mar 2014 in reply to danparker276 Link to this post

    Ok, so I had to Add the Themes directory and all the themes to my projects, Telerik wizard/upgrade didn't do it.  I also have to add this to the merged dictionaries on the app.xaml.

     Now i can see it.  I really don't like having to add a themes directory and extra files.  Now I can see it on my preview.
    I also have to add all the following lines, instead of just having 1 telerik line:
    xmlns:telerikInput="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Input"
    xmlns:telerikControls="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls"
    xmlns:telerikReporting="clr-namespace:Telerik.Reporting;assembly=Telerik.Reporting"
    Don't like to have to do this either.
    Have to add bindings on the appconfig even if I have the latest reporting.
    Also have to add styles

    And now my WPF program won't compile because it's saying:
    Error 11 The name "PickerToggleButton" does not exist in the namespace "clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls". ...\Themes\OfficeBlack\Telerik.Windows.Controls.xaml 1 1 LawtimeMain

    I'm like on 5 hours trying to install the WPF and reporting latest update.
  3. DevCraft banner
  4. Answer
    Stef
    Admin
    Stef avatar
    3053 posts

    Posted 04 Mar 2014 Link to this post

    Hi Dan,

    The only XAML file belonging to Telerik Reporting is Telerik.ReportViewer.Wpf.xaml. The rest of the files should be upgraded with the references to to Telerik UI for WPF, and should be of the corresponding version.

    Please test the following:
    1. For the selected themes, copy the UI for WPF XAML files into the project and add the Telerik Reporting Telerik.ReportViewer.Wpf.xaml file.
    2. Verify the resources are located properly in the declared resources - Setting a Theme (Using Implicit Styles).
    3. Add binding redirects as the current Q1 2014 Telerik Reporting version is yet built against Ui for WPF Q3 2013. We are going to provide a new build soon that will use Q1 2014 of Telerik UI for WPF.

    If the UI for WPF XAML files are not updated in the project you can get errors as the described, due to incompatibility of the used WPF assemblies and XAML files.

    I hope this helps you.


    Regards,
    Stef
    Telerik

    DevCraft Q1'14 is here! Join the free online conference to see how this release solves your top-5 .NET challenges. Reserve your seat now!

  5. danparker276
    danparker276 avatar
    389 posts
    Member since:
    Aug 2010

    Posted 04 Mar 2014 in reply to danparker276 Link to this post

    Ok, my fault on the last part.  I thought I could take the themes directory from the new Demos and put it in my project, but it's using old wpf themes xamls.  Seems to be going now.
  6. danparker276
    danparker276 avatar
    389 posts
    Member since:
    Aug 2010

    Posted 04 Mar 2014 Link to this post

    The size of my app seemed to grow 10MB also.
  7. Answer
    Stef
    Admin
    Stef avatar
    3053 posts

    Posted 07 Mar 2014 Link to this post

    Hello Dan,

    The size of the application should be the same or smaller, as the XAML is not included in the assemblies, and only the needed theme is loaded.

    Let us know if you have any concerns.

    Regards,
    Stef
    Telerik

    DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.

  8. danparker276
    danparker276 avatar
    389 posts
    Member since:
    Aug 2010

    Posted 07 Mar 2014 in reply to Stef Link to this post

    ok, i think i added extra themes or something
  9. Scott
    Scott avatar
    43 posts
    Member since:
    Nov 2007

    Posted 07 Mar 2014 in reply to danparker276 Link to this post

    same problem.  I added the themes folder (which I hate!) and merged dictionaries and I get :

    Error 11 The name "PickerToggleButton" does not exist in the namespace "clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls". C:\Users\Scott\Source\Repos\tools\Order Manager 2012\Client\Themes\OfficeBlack\Telerik.Windows.Controls.xaml 1934 12 Client

    What's going on telerik?  I don't want your themes, I just want my app to work after upgrading to your "latest"
  10. Nasko
    Admin
    Nasko avatar
    909 posts

    Posted 12 Mar 2014 Link to this post

    Hello Scott,

    This issue is usually caused by using the wrong version of the resources/themes for the WPF Report Viewer. The themes in C:\Program Files (x86)\Telerik\Reporting Q1 2014\Wpf\Themes work with version 2013.3.1202.40 of the UI for WPF. In order to use the newer assemblies of UI for WPF (Q1 2014) you need to update the themes as well. You can follow these steps to do so:
    1. You need to reference the Telerik.ReportViewer.Wpf.xaml resource file from the default installation folder: C:\Program Files (x86)\Telerik\Reporting Q1 2014\Wpf\Themes\<theme name>\Telerik.ReportViewer.Wpf.xaml. Since you are using newer version of the UI for WPF only this resource file will come from the Telerik Reporting installation folder.
    2. Then from the installed Q1 2014 UI for WPF, you need to reference the required Telerik.Windows.Controls assemblies (NoXAML) and the following XAML resources: System.Windows.xaml, Telerik.Windows.Controls.xaml, Telerik.Windows.Controls.Input.xaml, Telerik.Windows.Controls.Navigation.xaml.

    Another solution is to download and install the latest internal build of Telerik Reporting Q1 2014 8.0.14.311, which is built against UI for WPF Q1 2014. Thus, you will be able to copy all of the needed resources directly from the C:\Program Files (x86)\Telerik\Reporting Q1 2014\Wpf\Themes folder and the viewer should work correctly.

    If you experience any issues following the above suggestions it would be of great help for us if you open a support ticket where you can zip and attach a sample project exhibiting the described issue. Once we review it, we would be able to provide you with more information.

    Regards,
    Nasko
    Telerik
     

    DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.

     
Back to Top
DevCraft banner