Problems building solution using visualstudio.com msbuild process

3 posts, 0 answers
  1. Phoenix
    Phoenix avatar
    17 posts
    Member since:
    Feb 2015

    Posted 22 Jul 2016 Link to this post

    Hi, 

    We're currently trying to setup a build server using visual studio online, and one of the projects in our solution uses the wpf Report viewer.  We're getting the following errors while that particular project builds.  Would you be able to help?

    MSLCRM2\MSLCRM2\Themes\Office2013\Telerik.ReportViewer.Wpf.xaml (13, 6)
    The tag 'VisibilityConverter' does not exist in XML namespace 'clr-namespace:Telerik.ReportViewer.Wpf;assembly=Telerik.ReportViewer.Wpf'. Line 13 Position 6.

    MSLCRM2\MSLCRM2\Themes\OfficeBlack\Telerik.ReportViewer.Wpf.xaml (31, 6)
    The tag 'VisibilityConverter' does not exist in XML namespace 'clr-namespace:Telerik.ReportViewer.Wpf;assembly=Telerik.ReportViewer.Wpf'. Line 31 Position 6.

    MSLCRM2\MSLCRM2\Themes\Windows8\Telerik.ReportViewer.Wpf.xaml (33, 6)
    The tag 'VisibilityConverter' does not exist in XML namespace 'clr-namespace:Telerik.ReportViewer.Wpf;assembly=Telerik.ReportViewer.Wpf'. Line 33 Position 6.

     

    Note: I found this thread and tried to follow the advice in there, but it hasn't worked http://www.telerik.com/forums/build-failure

  2. Stef
    Admin
    Stef avatar
    3610 posts

    Posted 22 Jul 2016 Link to this post

    Hello Andrew,

    Please test the following:
    1. If you are not using Telerik UI for WPf as a separate product:
      Check which version of Telerik Reporting is used in the project and copy all XAML files from the corresponding installation folder of Telerik Reporting - C:\Program Files (x86)\Telerik\Reporting <VERSION>\Wpf. Then copy Telerik Ui for WPF assemblies located in C:\Program Files (x86)\Telerik\Reporting <VERSION>\Examples\CSharp\WpfDemo\bin.
    2. If you have Telerik Ui for WPF as a separate product.
      Check which version of Telerik Reporting is used in the project and that Telerik UI for WPF assemblies are considered with that version - WPF ReportViewer Dependencies.
      Then copy the following NoXAMLBinaries from Telerik UI for WPF installation folder:
      Telerik.Windows.Controls.dll
      Telerik.Windows.Controls.Input.dll
      Telerik.Windows.Controls.Navigation.dll
      Telerik.Windows.Data.dll

      Finally, copy the corresponding XAML files from Telerik UI for WPF installation folder.
      System.Windows.xaml
      Telerik.Windows.Controls.xaml
      Telerik.Windows.Controls.Input.xaml
      Telerik.Windows.Controls.Navigation.xaml

    In both cases, in the App.xaml test specifying the paths to XAML resources as follows:
    <Application.Resources>
       <ResourceDictionary>
         <ResourceDictionary.MergedDictionaries>
           <ResourceDictionary Source="/MyProject_Assembly_Name;component/Themes/System.Windows.xaml"/>
           <ResourceDictionary Source="/MyProject_Assembly_Name;component/Themes/Telerik.Windows.Controls.xaml"/>
           <ResourceDictionary Source="/MyProject_Assembly_Name;component/Themes/Telerik.Windows.Controls.Input.xaml"/>
           <ResourceDictionary Source="/MyProject_Assembly_Name;component//Themes/Telerik.Windows.Controls.Navigation.xaml"/>
           <ResourceDictionary Source="/MyProject_Assembly_Name;component//Themes/Telerik.ReportViewer.Wpf.xaml"/>
         </ResourceDictionary.MergedDictionaries>
       </ResourceDictionary>
     </Application.Resources>
    If you are using Telerik UI for WPF binaries with XAML in them, you can use them as resources.


    Regards,
    Stef
    Telerik by Progress
    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
  3. Senthil
    Senthil avatar
    6 posts
    Member since:
    Jul 2017

    Posted 16 Jan 2018 in reply to Stef Link to this post

    I tried this. This is still not working. I have followed the above described approach. 

    Titan.Reporting.Client\Reports.xaml(17):Titan.Reporting.Client\Reports.xaml(17,10): Error MC3074: The tag 'ReportViewer' does not exist in XML namespace 'http://schemas.telerik.com/wpf'. Line 17 Position 10.
    Titan.Reporting.Client\Themes\System.Windows.xaml(468):Titan.Reporting.Client\Themes\System.Windows.xaml(468,26): Error MC3074: The tag 'ButtonChrome' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls.Chromes;assembly=Telerik.Windows.Controls'. Line 468 Position 26.
    Titan.Reporting.Client\Themes\Telerik.ReportViewer.Wpf.xaml(47):Titan.Reporting.Client\Themes\Telerik.ReportViewer.Wpf.xaml(47,6): Error MC3074: The tag 'VisibilityConverter' does not exist in XML namespace 'clr-namespace:Telerik.ReportViewer.Wpf;assembly=Telerik.ReportViewer.Wpf'. Line 47 Position 6.
    Titan.Reporting.Client\Themes\Telerik.Windows.Controls.Input.xaml(23):Titan.Reporting.Client\Themes\Telerik.Windows.Controls.Input.xaml(23,6): Error MC3074: The tag 'ColorToBrushConverter' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls'. Line 23 Position 6.
    Titan.Reporting.Client\Themes\Telerik.Windows.Controls.Navigation.xaml(30):Titan.Reporting.Client\Themes\Telerik.Windows.Controls.Navigation.xaml(30,6): Error MC3074: The tag 'BooleanToVisibilityConverter' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls'. Line 30 Position 6.
    Titan.Reporting.Client\Themes\Telerik.Windows.Controls.xaml(21):Titan.Reporting.Client\Themes\Telerik.Windows.Controls.xaml(21,6): Error MC3074: The tag 'DragDropBooleanToVisibilityConverter' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls'. Line 21 Position 6.
    Process 'msbuild.exe' exited with code '1'.

     

Back to Top