GanttView Getting Started

4 posts, 0 answers
  1. Ed
    Ed avatar
    1 posts
    Member since:
    Sep 2017

    Posted 17 Sep Link to this post

    Hi -

    I'm trying to familiarize myself with the RadGanttView for WPF and am working through the Getting Started section of the documentation. However, when I create a new WPF app (Visual Studio 2017, .Net 4.6.1), add the listed references, add the namespace to the main window and then add a RadGanttView control to the XAML, the test app does not display the empty Gantt View. The window XAML is below. Getting up to speed with the RadGridView was quite easy with the documentation and I was hoping that the RadGanttView would be likewise.

    <Window x:Class="TelerikGantt.MainWindow"
            xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
            xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
            xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
            xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
            xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"
            xmlns:local="clr-namespace:TelerikGantt"
            mc:Ignorable="d"
            Title="MainWindow" Height="350" Width="525">
        <Grid>
            <telerik:RadGanttView x:Name="ganttView" />
        </Grid>
    </Window>

  2. Vladimir Stoyanov
    Admin
    Vladimir Stoyanov avatar
    23 posts

    Posted 19 Sep Link to this post

    Hi Ed,

    Can you please check if you have added NoXaml Binaries to your project? They don't have any default styles or ControlTemplates and this would be why nothing is displayed. If that is the case you can add a theme which is located in the Binaries.NoXaml folder. Then you can include the ResourceDictionaries you need to use in the resources of your window or application. If you choose the Office_Black theme for the RadGanttView, the ResourceDictionary will look like this:

    <ResourceDictionary>
                <ResourceDictionary.MergedDictionaries>
                    <ResourceDictionary Source="/Telerik.Windows.Themes.Office_Black;component/Themes/System.Windows.xaml"/>
                    <ResourceDictionary Source="/Telerik.Windows.Themes.Office_Black;component/Themes/Telerik.Windows.Controls.xaml"/>
                    <ResourceDictionary Source="/Telerik.Windows.Themes.Office_Black;component/Themes/Telerik.Windows.Controls.GanttView.xaml"/>
     
                </ResourceDictionary.MergedDictionaries>
    </ResourceDictionary>

    You can read more about how to set up NoXaml Binaries in the Setting a Theme article.

    I hope you find this helpful. Let me know if I can be of any further assistance.

    Regards,
    Vladimir Stoyanov
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
  3. Michael
    Michael avatar
    1 posts
    Member since:
    Sep 2017

    Posted 19 Sep in reply to Vladimir Stoyanov Link to this post

    That took care of it. I had the Office 2016 theme dll referenced, but did not have the theme for the GanttView added to the ResourceDictionary. Thank you for your help.

    I'm getting up to speed with Telerik's WPF controls and I've been impressed so far with the documentation and support.

  4. Vladimir Stoyanov
    Admin
    Vladimir Stoyanov avatar
    23 posts

    Posted 20 Sep Link to this post

    Hi Ed,

    I am glad to hear that you found my reply helpful and that your experience so far has been pleasant.

    Don't hesitate to contact us again if you have any more questions.

    Regards,
    Vladimir Stoyanov
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
Back to Top