Expression Dark theme throws errors after Telerik UI update

5 posts, 0 answers
  1. Patrick
    Patrick avatar
    8 posts
    Member since:
    May 2015

    Posted 20 Aug 2015 Link to this post

    I am in the process of updating our program from the WPF UI 2013.3 controls to 2015.2. I'm close to completing the changes I need, but I still can't build because I'm getting errors in my ResourceDictionaries:
    <ResourceDictionary Source="/Telerik.Windows.Themes.Expression_Dark;component/Themes/Telerik.Windows.Controls.xaml"/>
    <ResourceDictionary Source="/Telerik.Windows.Themes.Expression_Dark;component/Themes/Telerik.Windows.Controls.Input.xaml"/>
    <ResourceDictionary Source="/Telerik.Windows.Themes.Expression_Dark;component/Themes/Telerik.Windows.Controls.GridView.xaml"/>

     All 3 of these (but not the other controls) are throwing the following error when I try to build:

    An error occurred while finding the resource dictionary "/Telerik.Windows.Themes.Expression_Dark;component/Themes/Telerik.Windows.Controls.xaml" .CompanySoftwareName\OurFilePath\App.xaml

     

    I checked my Expression Dark dll file and noticed that it was referencing the 2013.3.xxx versions of the UI files in question, so I tried copy/pasting the 2015.2.xxx value in those locations, but this wasn't successful.
    Is there a new version of this expression dark dll that I need? What am I missing?
    I'd be glad to hear any suggestions from other users, or support from Telerik staff directly.

    Thank you!

     



  2. Patrick
    Patrick avatar
    8 posts
    Member since:
    May 2015

    Posted 20 Aug 2015 in reply to Patrick Link to this post

    I believe I solved my own problem. I found the 2015 dll for the expression dark theme and dropped it in the assemblies so it used the correct path to the rest of the control xaml files.

    It took a LOT of fishing around but it looks like it works.

    It broke my Telerik reports, though. :( Still using the 2013 report designer. It's throwing here:

            <tr:ReportViewer
                Name="reportViewerControl"
                ViewMode="PrintPreview" Loaded="reportViewerControl_Loaded">


            </tr:ReportViewer>

     

    tr is the following namespace:
    xmlns:tr="http://schemas.telerik.com/wpf"

    It's throwing a xaml parse exception:
    'The invocation of the constructor on type 'Telerik.ReportViewer.Wpf.ReportViewer' that matches the specified binding constraints threw an exception.' 

  3. UI for WPF is Visual Studio 2017 Ready
  4. Nasko
    Admin
    Nasko avatar
    909 posts

    Posted 21 Aug 2015 Link to this post

    Hello Patrick,

    Please review the The WPF/Silverlight report viewer is blank after upgrading from version prior to Q1 2014 to Q1 2014 or later KB article which elaborates on issues when upgrading Telerik Reporting and/or UI for WPF.

    In case the issue persists after troubleshooting it according to the provided KB article, please open a new support ticket for the Telerik Reporting product where you can zip and attach a sample project reproducing the issue.

    Regards,
    Nasko
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  5. Patrick
    Patrick avatar
    8 posts
    Member since:
    May 2015

    Posted 21 Aug 2015 in reply to Nasko Link to this post

    Thank you.

    I've updated to the 2015 Q2 reporting tool, and I'm blocked now due to ReportViewerModel being inaccessible due to being internal:

    RadToolBarPanel toolbar = this.reportViewerControl.ChildrenOfType<RadToolBarPanel>().FirstOrDefault();
                var vm = toolbar.DataContext as ReportViewerModel;
                vm.IsExportEnabled = true;

     I tried the solution found at this link:
    http://www.telerik.com/forums/sl-reportview---add-buttons-commands

    but it didn't make any difference whether I used safe casting or direct casting.

    It was working fine with the 2013 telerik reporting tools but does not anymore.

    I suppose this thread has meandered a bit, so if there's a better way for us to communicate for support on this issue, please let me know.

  6. Nasko
    Admin
    Nasko avatar
    909 posts

    Posted 24 Aug 2015 Link to this post

    Hello Patrick,

    As of Telerik Reporting Q3 2014, the WPF ReportViewer's ReportViewerModel is internal (no longer accessible). Instead, you can use the exposed viewer's API.

    To continue the communication on the topic, please open a new support ticket in the Telerik Reporting product category.

    Regards,
    Nasko
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top
UI for WPF is Visual Studio 2017 Ready